Desktop screen sharing over HTTP
First Claim
1. A system comprising:
- a web server, wherein the web server is not a proxy server;
the web server comprising a processor and a memory; and
a module on the web server configured to cause the processor to;
receive a communication comprising a secure or non-secure HTTP GET or POST command from a host computer requesting a session on the web server;
in response to receiving the communication, establish the session on the web server and assign a session-specific identifier to the session;
receive an HTTP POST or GET command from the host computer to receive an encoded screen image from the host computer using a codec;
receive a communication comprising an HTTP GET or POST command from a client computer requesting to join the session on the web server;
send to the client computer the encoded screen image via an HTTP POST or GET command;
receive a device input event originating at the client computer via an HTTP POST or GET command; and
send to the host computer the device input event via an HTTP POST or GET command, the device input event being processed at the host computer to enable the client to act as master for input device input of the host computer.
2 Assignments
0 Petitions
Accused Products
Abstract
Sharing a desktop screen is implemented on a Hypertext Transfer Protocol (HTTP) web server using variable interval GET and POST requests. Connection to a web server bypasses firewall or shared IP limitations. In the described HTTP/HTTPS only solution, an existing web server is used to allow one or more clients to view a remote computer'"'"'s screen and control it (remoting). The web server can act as an intermediary to enable one computer to “take control” of a second computer by enabling the first computer (a client) to view the desktop session of the second computer (a host) and enable the first computer to act as master for input device input (e.g., keyboard input, mouse input, stylus input, etc.) for the second computer.
18 Citations
20 Claims
-
1. A system comprising:
-
a web server, wherein the web server is not a proxy server; the web server comprising a processor and a memory; and a module on the web server configured to cause the processor to; receive a communication comprising a secure or non-secure HTTP GET or POST command from a host computer requesting a session on the web server; in response to receiving the communication, establish the session on the web server and assign a session-specific identifier to the session; receive an HTTP POST or GET command from the host computer to receive an encoded screen image from the host computer using a codec; receive a communication comprising an HTTP GET or POST command from a client computer requesting to join the session on the web server; send to the client computer the encoded screen image via an HTTP POST or GET command; receive a device input event originating at the client computer via an HTTP POST or GET command; and send to the host computer the device input event via an HTTP POST or GET command, the device input event being processed at the host computer to enable the client to act as master for input device input of the host computer. - View Dependent Claims (2, 3, 4, 5, 6, 7)
-
-
8. A method comprising:
-
receiving a communication on a web server from a host computer, the communication comprising an HTTP GET or POST command, the host computer requesting a session on the web server, wherein the web server is not a proxy server; in response to receiving the communication, establishing the session on the web server; sending from the web server to the host computer, a session-specific identifier identifying the established session via an HTTP POST or GET command; receiving at the web server an HTTP POST or GET command from the host computer, the HTTP POST or GET comprising an encoded screen image; receiving at the web server a communication comprising an HTTP GET or POST command from a client computer requesting to join the session identified by the session-specific identifier; sending the encoded screen image from the web server to the client computer; receiving at the web server a device input event originating at the client computer via an HTTP POST or GET command; and sending the device input event via an HTTP POST or GET command from the web server to the host computer, such that the client computer acts as master for the host computer'"'"'s input device input. - View Dependent Claims (9, 10, 11, 12, 13, 14)
-
-
15. A computer-readable storage device comprising computer-executable instructions which when executed cause at least one processor to:
-
receive a communication comprising an HTTP GET or POST command from a host computer requesting a session on a web server; in response to receiving the communication, establish the session on the web server and assign a session-specific identifier to the session; receive at least one HTTP POST or GET command of a plurality of HTTP POST commands from the host computer, the at least one HTTP POST or GET command comprising an encoded screen image; store the encoded screen image of the at least one HTTP POST or GET command in a cache on the web server; receive a communication comprising an HTTP GET or POST command from a client computer requesting to join the session on the web server; send to the client computer screen image data stored in the cache via an HTTP POST or GET command; receive a device input event originating at the client computer via an HTTP POST or GET command; and send to the host computer the device input event via an HTTP POST or GET command, the device input event being processed at the host computer to enable the client computer to act as master for input device input of the host computer. - View Dependent Claims (16, 17, 18, 19, 20)
-
Specification