Abstract: A system and method of implementing a virtual channel virtual private network is disclosed. In one embodiment, a remote desktop protocol (RDP) client is connected to a RDP server. The RDP client requests a virtual connection to a first computing device. A virtual channel for the RDP connection is created. A client application or client gateway is bound to the first virtual channel at the RDP client. The RDP server establishes a connection to a server application or a server gateway, and binds the connection to the first virtual channel.

Abstract: In particular embodiments, a method includes receiving from an application a first graphics device interface (GDI) call and adding the first GDI call to a list of events. The method further includes receiving from the application one or more second GDI calls, wherein each of the second GDI calls is related to the first GDI call and adding the second GDI calls to the list of events. The method further includes receiving from the application a third GDI call, wherein the third GDI call is not related to the first GDI call, and performing a call to a GDI system, the call including the list of events.

Abstract: In particular embodiments, a client device may established a first connection to a ticket server of a gateway, wherein the gateway couples the client device to a first computing device, retrieve a permission vector from the ticket server though the first connection, wherein the retrieved permission vector contains at least one or more tickets to authenticate and authorize the client device access to at least the gateway and the first computing device, and establish a second connection to the first computing device based at least on the retrieved tickets

Abstract: In particular embodiments, a first computing device may receive a request from a second computing device to access a first entity of an infrastructure, the second computing device being coupled to the first computing device, then determining an eligibility of the second computing device to access as least the first entity of the infrastructure, and if the second computing device is determined to be eligible to access the first entity, then assigning a second ticket to the second computing device responsive to the received request.

Abstract: A system and method of client side redirection with pluggable authentication and authorization is disclosed. In a particular embodiment, an operating system of a first computing device receives a request to cause remote desktop protocol (RDP) client device to connect to a second computing device. The client is coupled to the first computing device via a first RDP connection. The first computing device may use information associated with the first RDP connection to qualify the client to connect to the second computing device. If qualified, first computing device may send a redirect instruction to the client that redirects the client from the first computing device to the second computing device. The first computing device may send credentials to the client for use in establishing a second RDP connection to the second computing device. The redirect instruction and credentials may be sent via a virtual channel of the first RDP connection.

Abstract: A remoting client can be configured to offload various graphics-based remoting protocol processes to the GPU to thereby free up the CPU for performing other remoting tasks. In this way, a remoting client can be executed on a client terminal that has a less powerful CPU even when a graphics-rich desktop is virtualized on the client terminal. When the remoting client receives remoting communications containing graphics display data, the remoting client can write the graphics display data to a location in memory that is accessible to the GPU and can then pass the graphics display data to the GPU for further processing. The CPU is therefore freed from having to fully process the graphics display data including from having to copy the graphics display data to a display buffer.

Abstract: A remoting client can be configured to offload various graphics-based remoting protocol processes to the GPU to thereby free up the CPU for performing other remoting tasks. In this way, a remoting client can be executed on a client terminal that has a less powerful CPU even when a graphics-rich desktop is virtualized on the client terminal. When the remoting client receives remoting communications containing graphics display data, the remoting client can write the graphics display data to a location in memory that is accessible to the GPU and can then pass the graphics display data to the GPU for further processing. The CPU is therefore freed from having to fully process the graphics display data including from having to copy the graphics display data to a display buffer.

Abstract: Synchronization of audio and video data can be enforced by embedding audio within video frame data. In a network environment in which audio and video data are generated on a source computing device and then transferred over the network to a destination computing device for output, the source computing device can be configured to encode the video data into an encoded video stream. As part of this encoding, the source computing device can also embed audio in the encoded video stream in a manner that associates the audio with corresponding video frames. The encoded video stream with the embedded audio can then be transferred over the network. The destination computing device can be configured to parse the encoded video stream to remove the audio and route it to an audio buffer and then route the encoded video stream to a GPU.

Abstract: A secure access client can be employed to enforce limitations on a user's access to a file while also allowing the user to access the file using an application of choice. To provide this functionality, the secure access client can implement an RDP client that is configured to create an RDP session with an RDP service executing on the same computing device. The RDP service can allow the secure access client to display the user interface of an application employed to open a file. The secure access client can be configured to selectively apply access limitations on a per file basis. This selective enforcement can be accomplished by only implementing a virtual channel extension to provide a particular type of access to the file when the file's access limitations would allow such access.

Abstract: In particular embodiments, a first computing device associated with a web service may receive a connection from an HTML-compatible client. The first computing device may provide the client a script. A second computing device associated with the web service may receive connection information from the HTML-compatible client and assign the client a unique socket. The second computing device may launch a transcoding remote desktop client and receive a termination of the connection by the client.

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.

Abstract: A generic client engine can associate a transcoder process with a requested server-side application so that the transcoder process can act as an intermediary between the browser-based application and the server-side application. The transcoder process can be configured to communicate with the browser-based application using a browser-supported protocol. The transcoder process can be further configured to transcode between the browser-supported protocol and a protocol employed by the server-side application. In cases where a gateway service provides access to the server-side application, the transcoder process can also act as an intermediary between the browser-based application and the gateway service to transcode between the browser-supported protocol and a gateway protocol. In some cases, the transcoder process, and possibly the gateway service, can alternatively be located on the client device that hosts the browser-based application.

Abstract: A Native Client-based remote display client can efficiently perform multimedia redirection by routing un-rendered multimedia content to browser code executing outside the sandbox in which the remote display client is executed. In this way, a remote display client implemented as a Native Client module will not be limited to using the APIs available within the sandbox to render the multimedia content. The Native Client module can communicate with the browser code to provide parameters necessary for the browser code to submit a web-based request to the Native Client module via localhost to thereby obtain the multimedia content via one or more web-based communications.

Abstract: Many challenges exist for supporting computing devices over a network where the computing devices are incompatible with one another. Instead of providing a native remote desktop protocol (RDP) client for each device, RDP client functionality may be provided by a cross-platform scripting language client or agent. A cross-platform scripting language client of an RDP client transcodes any received RDP-compatible packets to a format supported by a cross-platform or standards-based web browser of the RDP client.

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.

Abstract: In particular embodiments, a computing device establishes a remote desktop connection with a remote host, the remote desktop connection including one or more dynamic virtual channels. The computing device receives from one or more sensors an indication that the computing device has been rotated to a new orientation. The computing device sends to the remote host, via one of the dynamic virtual channels, information associated with the new orientation. The computing device receives from the remote host graphical data based at least in part on the information associated with the new orientation and provides for display the graphical data.

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.

Abstract: In particular embodiments, a method includes receiving, by a computing device including an import/export framework, encoded client data. The client data may be encoded by a generic transcoding service. The method includes performing load-balancing based at least in part on the client data, authorizing the client's access of a remote application, and exporting the encoded client data to the remote application.

Abstract: In particular embodiments, a computing device may receive device data from a client device. The computing device may encode the data for transmission to a remote desktop client. The re-encoding may be performed according to a pre-defined import/export protocol.

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.