VNC client web application
Go to file
Joel Martin 5d8e7ec068 Add web-socket-js support with packet re-ordering.
- web-socket-js is from http://github.com/gimite/web-socket-js. It is
  a flash object that emultates WebSockets.

Unfortunately, events (or packets) from the web-socket-js object can
get re-ordered so we need to know the packet order.

- So wsproxy.py prepends the sequence number of the packet when
  sending.

- If the client receives packets out of order it queues them up and
  scans the queue for the sequence number it's looking for until
  things are back on track. Gross, but hey: It works!

- Also, add packet sequence checking to wstest.*
2010-04-17 17:24:14 -05:00
docs Add RFB specs and move *.js files into include/ 2010-03-31 19:43:09 -05:00
include Add web-socket-js support with packet re-ordering. 2010-04-17 17:24:14 -05:00
README.md List for proxy reasons. 2010-04-06 21:37:35 -05:00
TODO Add web-socket-js support with packet re-ordering. 2010-04-17 17:24:14 -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 stop routine stops mouseMove events too. 2010-04-14 23:40: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 Add web-socket-js support with packet re-ordering. 2010-04-17 17:24:14 -05:00
vnc.js Add web-socket-js support with packet re-ordering. 2010-04-17 17:24:14 -05:00
web.py Make web.py match README. Remove unused ws_echo.py. 2010-04-06 21:50:26 -05:00
wsproxy.py Add web-socket-js support with packet re-ordering. 2010-04-17 17:24:14 -05:00
wstest.html Add web-socket-js support with packet re-ordering. 2010-04-17 17:24:14 -05:00
wstest.py Add web-socket-js support with packet re-ordering. 2010-04-17 17:24:14 -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).