Remote desktop protocol client for a standards-based web browser
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.
1. A method comprising:
receiving at a remote desktop protocol (RDP) web client a packet; sending the received packet to a cross-platform scripting language client of the RDP web client wherein the RDP web client implements an RDP protocol using the cross-platform scripting language client;
creating a non-blocking thread by the cross-platform scripting language client at the RDP web client wherein the cross-platform scripting language client implements the RDP protocol by using a non-blocking thread to process the received packet;
determining a protocol data unit (PDU) type by the cross-platform scripting language client;
transcoding the received packet by the cross-platform scripting language client based, at least in part, on the determined PDU type, wherein transcoding comprises converting the received packet to a format supported by a cross-platform web browser of the RDP web client; and
displaying content from the received packet at the RDP web client via a web browser.
2. The method of claim 1 , further comprising:
establishing a socket connection between a web-socket server and an RDP server.
3. The method of claim 2 , wherein the RDP web client receives the packet from the RDP server via the web-socket server.
4. The method of claim 1 , wherein the cross-platform scripting language client is implemented using JAVASCRIPT.
5. The method of claim 1 , wherein the cross-platform scripting language client uses JAVASCRIPT to transcode the received packet.
6. The method of claim 1 , wherein HTML5 Canvas is used to render the content.
7. The method of claim 1 , wherein the received packet is in an RDP compatible format.
8. One or more computer-readable non-transitory storage media embodying software that is operable when executed to:
receive at a remote desktop protocol (RDP) web client a packet;
send the received packet to a cross-platform scripting language client of the RDP web client wherein the RDP web client implements an RDP protocol using the cross-platform scripting language client;
create a non-blocking thread by the cross-platform scripting language client at the RDP web client wherein the cross-platform scripting language client implements the RDP protocol by using a non-blocking thread to process the received packet;
determine a protocol data unit (PDU) type by the cross-platform scripting language client;
transcode the received packet by the cross-platform scripting language client based, at least in part, on the determined PDU type, wherein transcoding comprises converting the received packet to a format supported by a cross-platform web browser of the RDP web client; and
display content from the received packet at the RDP web client via a web browser.
9. The media of claim 8 , wherein the software is further operable when executed to:
establish a socket connection between a web-socket server and an RDP server.
10. The media of claim 9 , wherein the RDP web client receives the packet from the RDP server via the web-socket server.
11. The media of claim 8 , wherein the cross-platform scripting language client is implemented using JAVASCRIPT.
12. The media of claim 8 , wherein the cross-platform scripting language client uses JAVASCRIPT to transcode the received packet.
13. The media of claim 8 , wherein HTML5 Canvas is used to render the content.
14. An information handling system 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 at a remote desktop protocol (RDP) web client a packet; send the received packet to a cross-platform scripting language client of the RDP web client wherein the RDP web client implements an RDP protocol using the cross-platform scripting language client;
create a non-blocking thread by the cross-platform scripting language client at the RDP web client wherein the cross-platform scripting language client implements the RDP protocol by using a non-blocking thread to process the received packet;
determine a protocol data unit (PDU) type by the cross-platform scripting language client;
transcode the received packet by the cross-platform scripting language client based, at least in part, on the determined PDU type, wherein transcoding comprises converting the received packet to a format supported by a cross-platform web browser of the RDP web client; and
display content from the received packet at the RDP web client via a web browser.
15. The information handling system of claim 14 , wherein the processors are further operable when executing the instructions to:
establish a socket connection between a web-socket server and an RDP server.
16. The information handling system of claim 15 , wherein the RDP web client receives the packet from the RDP server via the web-socket server.
17. The information handling system of claim 14 , wherein the cross-platform scripting language client is implemented using JAVASCRIPT.
18. The information handling system of claim 14 , wherein the cross-platform scripting language client uses JAVASCRIPT to transcode the received packet.
19. The information handling system of claim 14 , wherein HTML5 Canvas is used to render the content.
20. The information handling system of claim 14 , wherein the received packet is in an RDP compatible format.