Abstract: An information handling system comprising a processor, a memory device, and a power management unit (PMU). The processor to execute computer readable program code of an interim edge storage management system, the processor operatively coupled to a client device, an edge storage device, and a plurality of remote network file hosting systems managed by the interim edge storage management system, wherein the interim edge storage management system includes a storage orchestrator to manage data storage of the client device at and access to the edge storage device and the plurality of remote network file hosting systems based on recency of usage of files to be stored.

Abstract: Examples of methods, systems, apparatus, and machine-readable storage media are provided to facilitate access and control of a remote desktop of a remote machine by a web browser at a client device through a transcoding server without installing proprietary plug-ins or protocols on the client device. A transcoding server may translate user input requests from a web browser into input calls compatible with a remote desktop display protocol. The transcoding server may receive remote desktop drawing commands from the remote machine and translate the remote desktop drawing commands into web browser drawing updates compatible with the web browser. A transcoding server may communicate with a web browser via HTTP and communicate with a remote machine via a remote desktop display protocol. A web browser may be an HTML5 browser. A transcoding server may send drawing coordinates to the web browser via an HTTP header and may use long polling.

Abstract: An RDP server may query a web client to determine one or more capabilities of the web client. The RDP server may receive a packet from the web client that indicates the one or more capabilities of the web client. The RDP server may identify one or more applications running on a remote machine to be accessed by the web client. The RDP server may provide one or more virtual channels between the RDP server and the web client. The one or more virtual channels may each be associated with an identified application running on the remote machine and a capability of the web client. The virtual channels may be provided to facilitate the generation of an interface for viewing and interacting with content of the remote machine at the web client.

Abstract: A web client may receive a first packet of audio data encoded in a first audio format from a web-socket server over a web socket connection between the web-socket server and the web client. The web client may convert the audio data such that the first packet is encoded in a second audio format, and the second audio format may be compatible with the web client. The web client may calculate a trip time for the first packet. The web client may send a second packet including an indication of the trip time to an RDP server by way of the web-socket server over a socket connection between the RDP server and the web-socket server. The web client may present the audio data using an audio canvas of the web client, and the audio data may be associated with an interface for viewing and interacting with a remote desktop.

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: 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: A web client may receive a first packet of audio data encoded in a first audio format from a web-socket server over a web socket connection between the web-socket server and the web client. The web client may convert the audio data such that the first packet is encoded in a second audio format, and the second audio format may be compatible with the web client. The web client may calculate a trip time for the first packet. The web client may send a second packet including an indication of the trip time to an RDP server by way of the web-socket server over a socket connection between the RDP server and the web-socket server. The web client may present the audio data using an audio canvas of the web client, and the audio data may be associated with an interface for viewing and interacting with a remote desktop.

Abstract: A web client may receive a run-length encoded packet of graphics data from a Remote Desktop Protocol server via a web-socket server. The web client may determine a run-length encoding algorithm for the packet based on a first color space associated with the packet. The web client may decompress the packet based on the determined run-length encoding algorithm, where decompressing the packet involves determining a plurality of commands to be performed on a canvas associated with the web client. The web client may render the graphics data on the canvas using the plurality of commands, wherein the graphics data is associated with a graphical interface for viewing and interacting with a remote desktop.

Abstract: An RDP server may query a web client to determine one or more capabilities of the web client. The RDP server may receive a packet from the web client that indicates the one or more capabilities of the web client. The RDP server may identify one or more applications running on a remote machine to be accessed by the web client. The RDP server may provide one or more virtual channels between the RDP server and the web client. The one or more virtual channels may each be associated with an identified application running on the remote machine and a capability of the web client. The virtual channels may be provided to facilitate the generation of an interface for viewing and interacting with content of the remote machine at the web client.

Abstract: A web client may receive a run-length encoded packet of graphics data from a Remote Desktop Protocol server via a web-socket server. The web client may determine a run-length encoding algorithm for the packet based on a first color space associated with the packet. The web client may decompress the packet based on the determined run-length encoding algorithm, where decompressing the packet involves determining a plurality of commands to be performed on a canvas associated with the web client. The web client may render the graphics data on the canvas using the plurality of commands, wherein the graphics data is associated with a graphical interface for viewing and interacting with a remote desktop.

Abstract: Examples of systems and methods are provided for communication and for forwarding display data and cursor type related to a remote session between a client device and a remote server. The system may facilitate establishing the remote session with the remote server. After the client device is connected to a remote session, it is determined if the style of the client device's cursor should be changed. The RDP client of the remote server creates the changed cursor based on bitmap details. The change cursor may be a 1-bit or 32-bit cursor. When the remote session is disconnected, the default cursor for the client device is re-instated at the client device.

Abstract: Examples of systems and methods are provided for communication and for establishing a remote session between a client device and a remote server using RDP. An RDP share option is enabled to notify the remote server of a request for a shared RDP session. Multiple client devices may connect to the single shared RDP session. One client device may be considered the presenter and given special permissions. Any other client devices may be considered attendees and given only restricted access. Multiple RDP sessions may be initiated for multiple client devices.

Abstract: Examples of systems and methods are provided for communication and for establishing a remote session between a client device and a remote server using RDP. An RDP share option is enabled to notify the remote server of a request for a shared RDP session. Multiple client devices may connect to the single shared RDP session. One client device may be considered the presenter and given special permissions. Any other client devices may be considered attendees and given only restricted access. Multiple RDP sessions may be initiated for multiple client devices.

Abstract: Examples of systems and methods are provided for communication and for forwarding display data and cursor type related to a remote session between a client device and a remote server. The system may facilitate establishing the remote session with the remote server. After the client device is connected to a remote session, it is determined if the style of the client device's cursor should be changed. The RDP client of the remote server creates the changed cursor based on bitmap details. The change cursor may be a 1-bit or 32-bit cursor. When the remote session is disconnected, the default cursor for the client device is re-instated at the client device.

Abstract: Examples of methods, systems, apparatus, and machine-readable storage media are provided to facilitate access and control of a remote desktop of a remote machine by a web browser at a client device through a transcoding server without installing proprietary plug-ins or protocols on the client device. A transcoding server may translate user input requests from a web browser into input calls compatible with a remote desktop display protocol. The transcoding server may receive remote desktop drawing commands from the remote machine and translate the remote desktop drawing commands into web browser drawing updates compatible with the web browser. A transcoding server may communicate with a web browser via HTTP and communicate with a remote machine via a remote desktop display protocol. A web browser may be an HTML5 browser. A transcoding server may send drawing coordinates to the web browser via an HTTP header and may use long polling.