VNC client web application
Go to file
Joel Martin 9f4af5a722 Hextile working. Improve latency by coallescing sends.
- Hextile has an undocumented weirdness where RAW frames are often
  followed by a 0 byte that should be ignored.

- Coallesce client messages that are one after another. Without
  this the server seems to often ignore frames that are send right
  after another frame has been sent. This fixes a reconnect issue
  where setEncodings seems to be ignored. Also results in a huge
  performance increase after key strokes (by adding a update request
  to the key event message) because the server always sends an update
  instead of sometimes waiting for the next poll to be sent.
2010-04-13 12:59:11 -05:00
docs Add RFB specs and move *.js files into include/ 2010-03-31 19:43:09 -05:00
include Switch to much faster console.log and separate utils into util.js. 2010-04-13 09:28:53 -05:00
README.md List for proxy reasons. 2010-04-06 21:37:35 -05:00
canvas.html Switch to much faster console.log and separate utils into util.js. 2010-04-13 09:28:53 -05:00
canvas.js Remove event handlers on disconnect. 2010-04-13 09:39:29 -05:00
prime.html WebWorkers example with two way messages. 2010-04-10 15:52:27 -04: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 Remove event handlers on disconnect. 2010-04-13 09:39:29 -05:00
vnc.js Hextile working. Improve latency by coallescing sends. 2010-04-13 12:59:11 -05:00
web.py Make web.py match README. Remove unused ws_echo.py. 2010-04-06 21:50:26 -05:00
wsproxy.py Working with Raw rectangles and capital letter keys. 2010-04-05 23:54:30 -05:00

README.md

VNC HTML5 Client

Description

An VNC client implemented using HTML5, specifically Canvas and Web Sockets.

Requirements

  • A browser that supports Web Sockets (mostly Chrome as of Apr 6, 2010) and Canvas (most browsers)

  • Until VNC server support web sockets, you need to use a Web Sockets to normal socket proxy. There are a couple reasons for this:

    1. Web Sockets 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 Web Sockets 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 Web Sockets. The python proxy base64 encodes the data so that the Javascript client can base64 decode the data into an array.

Usage

  • run a VNC server.

    Xvnc :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).

  • Provide the host and port where the proxy is running and the password that the vnc server is using (if any).