Generic transcoding service with library attachment

• US 9,392,053 B2
• Filed: 02/21/2014
• Issued: 07/12/2016
• 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
• Primary Examiner(s): Kim, Hee Soo
• Assistant Examiner(s): Kassa, Elizabeth
• Application Number:
  US14/186,903
• Publication Number:
  US 20150244788A1
• Time in Patent Office: 872 Days
• Field of Search: 709/203
• US Class Current: 1/1
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• 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
• CPC Class Codes: H04L 67/565 Conversion or adaptation of application format or content adding application control or application functional data H04L67/561

Abstract

In particular embodiments, a method includes, by a computing device, receiving a connection from a client and assigning the client a unique socket. The method further includes launching a generic transcoding service attached to a runtime library, and the runtime library may be able to intercept system calls from a specific instance of an application executing on a remote client for exporting to the client. The method further includes receiving a termination of the connection by the client and updating load-balancing information.

Claims

1. A method comprising, by a computing device:

receiving a connection from a hypertext markup language (HTML) client, wherein the HTML client does not include functionality for a remote desktop protocol;

receiving connection information from the HTML client describing the connection;

assigning to the HTML client a unique socket;

launching by a generic client engine a remote desktop protocol (RDP) client with a generic transcoding service attached to a runtime library, wherein the runtime library is operable to intercept system calls from a specific instance of an application executing on a remote client for exporting to the HTML client, and wherein the launching is based, at least in part, on a socket specification associated with the unique socket;

defining by the generic transcoding service one or more functional primitives for import and export which allows for application extension for the HTML client, wherein the one or more functional primitives comprises HTML syntax and a stream service;

providing an interface to the HTML client with a remote desktop protocol (RDP) server via the stream service of the generic transcoding service such that the HTML client connects to an RDP server;

reconstructing, by the stream service, one or more tasks sent to and received from the RDP server;

obtaining a credential and information associated with the connection prior to launching the generic transcoding service;

providing a remote desktop client function via the stream service, wherein the remote desktop client function comprises interpreting, processing and transcoding one or more operations;

attaching the generic transcoding service to one or more device functions of the HTML client;

creating a plurality of channels, for the connection, associated with the generic transcoding service such that a plurality of independent streams of data are transported, wherein at least one of the plurality of channels is a control channel, and wherein at least one of the plurality of channels is a main channel;

establishing bidirectional communication over the control channel between the generic client engine and the generic transcoding service using a unique reference identifier for each instance of the generic transcoding service;

using the main channel to communicate between an HTML browser of the HTML client and the generic transcoding service;

communicating transcoded data via the main channel between the RDP server and the HTML browser of the client, wherein RDP server export and import of data occurs through the generic transcoding service;

managing communications of the RDP client via the generic transcoding service;

receiving a termination of the connection by the HTML client;

updating load-balancing information; and

selecting a host based, at least in part, on the load-balancing information.

2. The method of claim 1, wherein receiving a connection from the HTML client comprises receiving connection information from the HTML 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 HTML client is an HTTP-compatible thin client comprising a browser.

5. The method of claim 1, wherein the RDP client is a transcoding remote desktop client, wherein when the RDP client is launched a transcoding operation begins.

6. The method of claim 1, further comprising:

receiving, from the runtime library, one or more environmental variables via a control channel.

7. The method of claim 6, wherein the one or more environmental variables are utilized to validate operation for a reference identifier.

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 connection from a hypertext markup language (HTML) client, wherein the HTML client does not include functionality for a remote desktop protocol;

receiving connection information from the HTML client describing the connection;

assign to the HTML client a unique socket;

launch by a generic client engine a remote desktop protocol (RDP) client with a generic transcoding service attached to a runtime library, wherein the runtime library is operable to intercept system calls from a specific instance of an application executing on a remote client for exporting to the HTML client, and wherein the launch is based, at least in part, on a socket specification associated with the unique socket;

define by the generic transcoding service one or more functional primitives for import and export which allows for application extension for the HTML client, wherein the one or more functional primitives comprises HTML syntax and a stream service;

provide an interface to the HTML client with a remote desktop protocol (RDP) server via the stream service of the generic transcoding service such that the HTML client connects to an RDP server;

reconstructing, by the stream service, one or more tasks sent to and received from the RDP server;

obtain a credential and information associated with the connection prior to launching the generic transcoding service;

provide a remote desktop client function via the stream service, wherein the remote desktop client function comprises interpreting, processing and transcoding one or more operations;

attach the generic transcoding service to one or more device functions of the HTML client;

creating a plurality of channels, for the connection, associated with the generic transcoding service such that a plurality of independent streams of data are transported, wherein at least one of the plurality of channels is a control channel, and wherein at least one of the plurality of channels is a main channel;

establishing bidirectional communication over the control channel between the generic client engine and the generic transcoding service using a unique reference identifier for each instance of the generic transcoding service;

using the main channel to communicate between an HTML browser of the HTML client and the generic transcoding service;

communicating transcoded data via the main channel between the RDP server and the HTML browser of the client, wherein RDP server export and import of data occurs through the generic transcoding service;

managing communications of the RDP client via the generic transcoding service;

receive a termination of the connection by the HTML client;

update load-balancing information; and

select a host based, at least in part, on the load-balancing information.

9. The system of claim 8, wherein receiving a connection from the HTML client comprises receiving connection information from the HTML 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 HTML client is an HTTP-compatible thin client comprising a browser.

12. The system of claim 8, wherein the RDP client is a transcoding remote desktop client, wherein when the RDP client is launched a transcoding operation begins.

13. The system of claim 8, the processors being further operable when executing the instructions to:

receive, from the runtime library, one or more environmental variables via a control channel.

14. The system of claim 13, wherein the one or more environmental variables are utilized to validate operation for a reference identifier.

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

receive a connection from a hypertext markup language (HTML) client, wherein the HTML client does not include functionality for a remote desktop protocol;

receiving connection information from the HTML client describing the connection;

assign to the HTML client a unique socket;

launch by a generic client engine a remote desktop protocol (RDP) client with a generic transcoding service attached to a runtime library, wherein the runtime library is operable to intercept system calls from a specific instance of an application executing on a remote client for exporting to the HTML client and wherein the launch is based, at least in part, on a socket specification associated with the unique socket;

define by the generic transcoding service one or more functional primitives for import and export which allows for application extension for the HTML client, wherein the one or more functional primitives comprises HTML syntax and a stream service;

provide an interface to the HTML client with a remote desktop protocol (RDP) server via the stream service of the generic transcoding service such that the HTML client connects to an RDP server;

reconstructing, by the stream service, one or more tasks sent to and received from the RDP server;

obtain a credential and information associated with the connection prior to launching the generic transcoding service;

provide a remote desktop client function via the stream service, wherein the remote desktop client function comprises interpreting, processing and transcoding one or more operations;

attach the generic transcoding service to one or more device functions of the HTML client;

creating a plurality of channels, for the connection, associated with the generic transcoding service such that a plurality of independent streams of data are transported, wherein at least one of the plurality of channels is a control channel, and wherein at least one of the plurality of channels is a main channel;

establishing bidirectional communication over the control channel between the generic client engine and the generic transcoding service using a unique reference identifier for each instance of the generic transcoding service;

using the main channel to communicate between an HTML browser of the HTML client and the generic transcoding service;

communicating transcoded data via the main channel between the RDP server and the HTML browser of the client, wherein RDP server export and import of data occurs through the generic transcoding service;

managing communications of the RDP client via the generic transcoding service;

receive a termination of the connection by the HTML client;

update load-balancing information; and

select a host based, at least in part, on the load-balancing information.

16. The media of claim 15, wherein receiving a connection from the HTML client comprises receiving connection information from the HTML 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 HTML client is an HTTP-compatible thin client comprising a browser.

19. The media of claim 15, wherein the RDP client is a transcoding remote desktop client, wherein when the RDP client is launched a transcoding operation begins.

20. The media of claim 15, the software further operable when executed to:

receive, from the runtime library, one or more environmental variables via a control channel.