emscripten/third_party/websockify, branch 1.3.3 Emscripten: An LLVM-to-JavaScript Compiler https://git.amat.us/emscripten/atom/third_party/websockify?h=1.3.3 2012-12-19T23:06:48Z Updated scripts to call python2 directly rather than relying on python symlink pointing to the right place. See PEP394 for details on why this should be OK. 2012-12-19T23:06:48Z Alan Kligman alan.kligman@gmail.com 2012-12-01T23:31:36Z urn:sha1:315f13e5a1b35e23241da080f0df16e80ece88ae Update websockify, fix websocket tests, refactor websocket harness. 2012-11-01T14:22:08Z Joel Martin github@martintribe.org 2012-10-31T20:51:23Z urn:sha1:99e238901bcdce6d8e6ef32b310c64a6fca0216b - pull in websockify c00c0eed from https://github.com/kanaka/websockify with one-shot socket listener cleanup and other misc updates. - import the WebSocketProxy class directly and launch it one-shot using the run_once parameter rather than spawning a separate websockify via shell. - create a python version of socket_server.sh and in the harness and remove socket_server.sh. - refactor clean_pids to use a two phase cleanup where it sends a SIGTERM (to give the parent the chance to cleanup children) and then send a SIGTERM 1 second later. This still has risk of leaving child processes around (for example, the nc process in the original socket_server.sh which would also hold onto the listen port). Conflicts: tests/runner.py update websockify to latest trunk 2012-10-30T17:52:24Z Alon Zakai alonzakai@gmail.com 2012-10-30T17:52:24Z urn:sha1:fcb6c33bac763d7a8246674eff33b599c28c1b6e initial (not-yet-working) sockets implementation 2012-09-27T23:11:55Z Alon Zakai alonzakai@gmail.com 2012-09-27T23:11:55Z urn:sha1:31f7b2a5a65d2d640343013dac4bb836c3bfba5f