FRONT-END HIGH AVAILABILITY PROXY

• US 20150244787A1
• Filed: 02/21/2014
• Published: 08/27/2015
• Est. Priority Date: 02/21/2014
• Status: Active Grant

• Current Assignee: Dell Products LP (Dell Technologies Inc.)
• Original Assignee: Dell Products LP (Dell Technologies Inc.)
• Inventors: Fausak, Andrew T., Rombakh, Oleg
• Granted Patent: US 9,553,925 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 67/1001 for accessing one among a plurality of replicated servers
• CPC Class Codes: H04L 67/56 Provisioning of proxy services store-and-forward switching systems in data switching networks H04L12/54

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.

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.

2. The method of claim 1, wherein receiving a connection from the client comprises receiving connection information from the client comprising credentials.

3. The method of claim 2, wherein the connection information is input by a user via a dialog menu.

4. The method of claim 1, wherein the client is an HTTP-compatible thin client comprising a browser.

5. The method of claim 1, wherein the transcoding remote desktop client comprises a generic transcoding service.

6. The method of claim 1, wherein the load-balancing information comprises the number of present connections on each of the plurality of execution hosts.

7. The method of claim 1, wherein the first execution host is selected based at least in part on one or more of the following:

the health of a front-end;

one or more ports;

one or more protocols;

one or more elevated protocols;

one or more services;

or

URL/URI.

14. The system of claim 1, wherein the first execution host is selected based at least in part on one or more of the following:

the health of a front-end;

one or more ports;

one or more protocols;

one or more elevated protocols;

one or more services;

or

URL/URI.

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.

9. The system of claim 8, wherein receiving a connection from the client comprises receiving connection information from the client comprising credentials.

10. The system of claim 9, wherein the connection information is input by a user via a dialog menu.

11. The system of claim 8, wherein the client is an HTTP-compatible thin client comprising a browser.

12. The system of claim 8, wherein the transcoding remote desktop client comprises a generic transcoding service.

13. The system of claim 8, wherein the load-balancing information comprises the number of present connections on each of the plurality of execution hosts.

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.

16. The media of claim 15, wherein receiving a connection from the client comprises receiving connection information from the client comprising credentials.

17. The media of claim 16, wherein the connection information is input by a user via a dialog menu.

18. The media of claim 15, wherein the client is an HTTP-compatible thin client comprising a browser.

19. The media of claim 15, wherein the transcoding remote desktop client comprises a generic transcoding service.

20. The media of claim 15, wherein the load-balancing information comprises the number of present connections on each of the plurality of execution hosts.