VNC client web application
Go to file
Joel Martin 1e633bc8ee wstest*. Fix Opera problems. Flash policy. Misc bugs.
Lame. Opera doesn't support javascript reduce().

Also, Opera seems to just plain be pathetic when it comes to
delivering the web-socket-js events. Around 1/5 to 1/3 of all received
packets are never received as an event at all.

- Change default delay for send side to 10ms.

- Use a textarea for errors so that even without console.* support
  (ala firebug) we still see the errors that are happening.
2010-04-19 10:41:06 -05:00
docs Add RFB specs and move *.js files into include/ 2010-03-31 19:43:09 -05:00
include Status/error refactor. Fix firefox bugs. 2010-04-18 18:43:03 -05:00
README.md README.md typo and clarify. 2010-04-18 20:57:34 -05:00
TODO Update README.md and TODO. 2010-04-18 20:53:54 -05:00
canvas.html Status/error refactor. Fix firefox bugs. 2010-04-18 18:43:03 -05:00
canvas.js Status/error refactor. Fix firefox bugs. 2010-04-18 18:43:03 -05:00
prime.html Remove mootools-more references. 2010-04-18 16:28:54 -05:00
prime.js WebWorkers example with two way messages. 2010-04-10 15:52:27 -04:00
rfb_notes First RFB protocol stub implementation. 2010-04-01 11:36:22 -05:00
vnc.html Send seq nums and b64 encode based on query string. 2010-04-18 20:35:43 -05:00
vnc.js Send seq nums and b64 encode based on query string. 2010-04-18 20:35:43 -05:00
web.py Make web.py match README. Remove unused ws_echo.py. 2010-04-06 21:50:26 -05:00
wsproxy.py Send seq nums and b64 encode based on query string. 2010-04-18 20:35:43 -05:00
wstest.html wstest*. Fix Opera problems. Flash policy. Misc bugs. 2010-04-19 10:41:06 -05:00
wstest.py wstest*. Fix Opera problems. Flash policy. Misc bugs. 2010-04-19 10:41:06 -05:00

README.md

VNC HTML5 Client

Description

A VNC client implemented using HTML5, specifically Canvas and WebSocket.

For browsers that do not have builtin WebSocket support, the project includes web-socket-js, a WebSocket emulator using Adobe Flash (http://github.com/gimite/web-socket-js).

Requirements

Until there is VNC server support for WebSocket connections, you need to use a WebSocket to TCP socket proxy. There is a python proxy included ('wsproxy').

There a few reasons why a proxy is required:

  1. WebSocket is not a pure socket protocol. There is an initial HTTP like handshake to allow easy hand-off by web servers and allow some origin policy exchange. Also, each WebSocket frame begins with 0 ('\x00') and ends with 255 ('\xff').

  2. Javascript itself does not have the ability to handle pure byte strings (Unicode encoding messes with it) even though you can read them with WebSocket. The python proxy encodes the data so that the Javascript client can base64 decode the data into an array. The client requests this encoding

  3. When using the web-socket-js as a fallback, WebSocket 'onmessage' events may arrive out of order. In order to compensate for this the client asks the proxy (using the initial query string) to add sequence numbers to each packet.

Usage

  • run a VNC server.

    vncserver :1

  • run the python proxy:

    ./wsproxy.py [listen_port] [vnc_host] [vnc_port]

    ./wsproxy.py 8787 localhost 5901

  • run the mini python web server to serve the directory:

    ./web.py PORT

    ./web.py 8080

  • Point your web browser at http://localhost:8080/vnc.html (or whatever port you used above to run the web server).

  • Specify the host and port where the proxy is running and the password that the vnc server is using (if any). Hit the Connect button and enjoy!