FRONT-END HIGH AVAILABILITY PROXY
First Claim
1. A method comprising, by one or more computing devices:
- receiving a first connection from a client;
assigning the client a unique socket;
selecting, from a plurality of execution hosts, a first execution host for the first connection based at least in part on load-balancing information associated with the execution hosts, wherein each execution host comprises a unique general client engine;
launching a first transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host;
receiving a second connection from the client, the second connection being associated with the unique socket of the first connection;
launching a second transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host; and
updating the load-balancing information.
14 Assignments
0 Petitions
Accused Products
Abstract
In particular embodiments, a method includes receiving a first connection from a client and assigning the client a unique socket. The method further includes selecting, from a plurality of execution hosts, a first execution host for the first connection based at least in part on load-balancing information associated with the execution hosts. Each execution host includes a unique general client engine. The method further includes launching a first transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host. The method further includes receiving a second connection from the client, the second connection being associated with the unique socket of the first connection, launching a second transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host, and updating the load-balancing information.
-
Citations
20 Claims
-
1. A method comprising, by one or more computing devices:
-
receiving a first connection from a client; assigning the client a unique socket; selecting, from a plurality of execution hosts, a first execution host for the first connection based at least in part on load-balancing information associated with the execution hosts, wherein each execution host comprises a unique general client engine; launching a first transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host; receiving a second connection from the client, the second connection being associated with the unique socket of the first connection; launching a second transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host; and updating the load-balancing information. - View Dependent Claims (2, 3, 4, 5, 6, 7, 14)
-
-
8. A system comprising:
-
one or more processors; and a memory coupled to the processors comprising instructions executable by the processors, the processors being operable when executing the instructions to; receive a first connection from a client; assign the client a unique socket; select, from a plurality of execution hosts, a first execution host for the first connection based at least in part on load-balancing information associated with the execution hosts, wherein each execution host comprises a unique general client engine; launch a first transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host; receive a second connection from the client, the second connection being associated with the unique socket of the first connection; launch a second transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host; and update the load-balancing information. - View Dependent Claims (9, 10, 11, 12, 13)
-
-
15. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:
-
receive a first connection from a client; assign the client a unique socket; select, from a plurality of execution hosts, a first execution host for the first connection based at least in part on load-balancing information associated with the execution hosts, wherein each execution host comprises a unique general client engine; launch a first transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host; receive a second connection from the client, the second connection being associated with the unique socket of the first connection; launch a second transcoding remote desktop client instance at the first execution host in association with the general client engine of the first execution host; and update the load-balancing information. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification