GENERAL CLIENT ENGINE WITH LOAD BALANCING FOR CLIENT-SERVER COMMUNICATION

• US 20130325934A1
• Filed: 06/14/2013
• Published: 12/05/2013
• Est. Priority Date: 06/01/2012
• Status: Active Grant

• Current Assignee: Dell Products BV (Dell Technologies Inc.)
• Original Assignee: Dell Products BV (Dell Technologies Inc.)
• Inventors: Fausak, Andrew T., Rombakh, Oleg
• Granted Patent: US 9,705,729 B2
• Time in Patent Office: Days
• US Class Current: 709/203
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/025 for remote control or remote monitoring of applications
• CPC Class Codes: H04L 67/1036 Load balancing of requests to servers for services different from user content provisioning, e.g. load balancing across domain name servers
• CPC Class Codes: H04L 67/133 Protocols for remote procedure calls [RPC]
• CPC Class Codes: H04L 69/162 involving adaptations of sockets based mechanisms secure socket layer H04L63/168

Abstract

In particular embodiments, a computing device receives a connection from an HTTP-compatible client. The device may assign the client a unique socket, launch a transcoding remote desktop client, receive a termination of the connection by the client, and update load-balancing information.

Claims

1. A method comprising, by a computing device:

receiving a connection from an HTTP-compatible client;

assigning the client a unique socket;

launching a transcoding remote desktop client;

receiving a termination of the connection by the client; and

updating 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 launching the transcoding remote desktop client is performed based at least in part on load-balancing information.

5. The method of claim 1, wherein launching the transcoding remote desktop client occurs based at least in part on the assigned socket.

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

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

8. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:

receive a connection from an HTTP-compatible client;

assign the client a unique socket;

launch a transcoding remote desktop client;

receive a termination of the connection by the client; and

update load-balancing information.

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

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

11. The media of claim 8, wherein launching the transcoding remote desktop client is performed based at least in part on load-balancing information.

12. The media of claim 8, wherein launching the transcoding remote desktop client occurs based at least in part on the assigned socket.

13. The media of claim 8, wherein the HTTP-compatible client is a thin client comprising a browser.

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

15. A system comprising:

a computing device comprising one or more processors; and

a memory coupled to the processors comprising instructions executable by the processors, the processors operable when executing the instructions to;

receive a connection from an HTTP-compatible client;

assign the client a unique socket;

launch a transcoding remote desktop client;

receive a termination of the connection by the client; and

update load-balancing information.

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

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

18. The system of claim 15, wherein launching the transcoding remote desktop client is performed based at least in part on load-balancing information.

19. The system of claim 15, wherein launching the transcoding remote desktop client occurs based at least in part on the assigned socket.

20. The system of claim 15, wherein the HTTP-compatible client is a thin client comprising a browser.