Joel Martin
d9aedfe7d3
*** IMPORTANT NOTE *** This is the last minor version to support the Hixie protocol. I may do bug fixes (e.g. 0.4.1) but 0.5.0 will drop the Hixie protocol support. The latest released version of all major browsers (and web-socket-js) support the IETF 6455 protocol. - Other changes: updating TODO and release process notes.
25 lines
942 B
Plaintext
25 lines
942 B
Plaintext
Some implementation notes:
|
|
|
|
There is an included flash object (web-socket-js) that is used to
|
|
emulate websocket support on browsers without websocket support
|
|
(currently only Chrome has WebSocket support).
|
|
|
|
Javascript doesn't have a bytearray type, so what you get out of
|
|
a WebSocket object is just Javascript strings. Javascript has UTF-16
|
|
unicode strings and anything sent through the WebSocket gets converted
|
|
to UTF-8 and vice-versa. So, one additional (and necessary) function
|
|
of wsproxy is base64 encoding/decoding what is sent to/from the
|
|
browser.
|
|
|
|
Building web-socket-js emulator:
|
|
|
|
cd include/web-socket-js/flash-src
|
|
mxmlc -static-link-runtime-shared-libraries WebSocketMain.as
|
|
|
|
Building release tarball:
|
|
- not really necessary since tagged revision can be downloaded
|
|
from github as tarballs
|
|
|
|
git archive --format=tar --prefix=websockify-${WVER}/ v${WVER} > websockify-${WVER}.tar
|
|
gzip websockify-${WVER}.tar
|