diff options
| author | Alon Zakai <alonzakai@gmail.com> | 2012-09-30 10:24:53 -0700 |
|---|---|---|
| committer | Alon Zakai <alonzakai@gmail.com> | 2012-09-30 10:24:53 -0700 |
| commit | b614f2bc5d9fc421565824b1ceb9a3384f26f35f (patch) | |
| tree | 243c47baa4c6ce4273a5743d79f3c0dbc78789e5 /third_party/websockify/docs/notes | |
| parent | c70758e3b49beb016a3d9db7b609c499d55de48b (diff) | |
| parent | 7eaa78060c34489c7e56193c725641303d520f31 (diff) | |
Merge branch 'incoming'
Diffstat (limited to 'third_party/websockify/docs/notes')
| -rw-r--r-- | third_party/websockify/docs/notes | 17 |
1 files changed, 17 insertions, 0 deletions
diff --git a/third_party/websockify/docs/notes b/third_party/websockify/docs/notes new file mode 100644 index 00000000..b3cc0cfb --- /dev/null +++ b/third_party/websockify/docs/notes @@ -0,0 +1,17 @@ +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 |