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

List for proxy reasons.

This commit is contained in:
Joel Martin 2010-04-06 21:37:35 -05:00
parent 5aeb98801b
commit d63e146209
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
README.md
View File

@ -18,15 +18,15 @@ Requirements
* Until VNC server support web sockets, you need to use a Web Sockets to * Until VNC server support web sockets, you need to use a Web Sockets to
normal socket proxy. There are a couple reasons for this: normal socket proxy. There are a couple reasons for this:
* Web Sockets is not a pure socket protocol. There is an initial HTTP 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 like handshake to allow easy hand-off by web servers and allow some
origin policy exchange. Also, each Web Sockets frame begins with origin policy exchange. Also, each Web Sockets frame begins with
0 ('\x00') and ends with 255 ('\xff'). 0 ('\x00') and ends with 255 ('\xff').
* Javascript itself does not have the ability to handle pure byte 2. Javascript itself does not have the ability to handle pure byte
strings (Unicode encoding messes with it) even though you can read strings (Unicode encoding messes with it) even though you can read
them with Web Sockets. The python proxy base64 encodes the data so them with Web Sockets. The python proxy base64 encodes the data so
that the Javascript client can base64 decode the data into an array. that the Javascript client can base64 decode the data into an array.
Usage Usage