jcarr
/
noVNC
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update requirements. Note WS added to libvncserver.

This commit is contained in:
Joel Martin 2011-10-08 12:57:57 -05:00
parent 1e50871599
commit a367e84a92
1 changed files with 4 additions and 17 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -38,10 +38,8 @@ See more screenshots <a href="http://kanaka.github.com/noVNC/screenshots.html">h
a WebSockets emulator using Adobe Flash. iOS 4.2+ has built-in a WebSockets emulator using Adobe Flash. iOS 4.2+ has built-in
WebSocket support. WebSocket support.
* Fast Javascript Engine: noVNC avoids using new Javascript * Fast Javascript Engine: this is not strictly a requirement, but
functionality so it will run on older browsers, but decode and without a fast Javascript engine, noVNC might be painfully slow.
rendering happen in Javascript, so a slow Javascript engine will
mean noVNC is painfully slow.
* I maintain a more detailed browser compatibility list <a * I maintain a more detailed browser compatibility list <a
href="https://github.com/kanaka/noVNC/wiki/Browser-support">here</a>. href="https://github.com/kanaka/noVNC/wiki/Browser-support">here</a>.
@ -50,23 +48,12 @@ See more screenshots <a href="http://kanaka.github.com/noVNC/screenshots.html">h
### Server Requirements ### Server Requirements
Unless you are using a VNC server with support for WebSockets Unless you are using a VNC server with support for WebSockets
connections (only my [fork of libvncserver](http://github.com/kanaka/libvncserver) connections (such as [x11vnc/libvncserver](http://libvncserver.sourceforge.net/)),
currently), you need to use a WebSockets to TCP socket proxy. There is you need to use a WebSockets to TCP socket proxy. There is
a python proxy included ('websockify'). One advantage of using the a python proxy included ('websockify'). One advantage of using the
proxy is that it has builtin support for SSL/TLS encryption (i.e. proxy is that it has builtin support for SSL/TLS encryption (i.e.
"wss://"). "wss://").
There a few reasons why a proxy is required:
1. WebSockets 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 WebSockets frame begins
with 0 ('\x00') and ends with 255 ('\xff').
2. Javascript itself does not have the ability to handle pure byte
arrays. The python proxy encodes the data as base64 so that the
Javascript client can decode the data as an integer array.
### Quick Start ### Quick Start