Joel Martin db6ae6c6a0 Issue #11: daemonize after opening listen port. ...

The listen port should be opened before daemonizing otherwise if
opening the port fails, the user will get no feedback. The only
complication was that the listen socket needs to not be closed as part
of daemonizing.

Thanks to http://github.com/rickr for finding it.

2010-07-17 12:05:58 -05:00

..

launch.sh

Launch script and reworked usage in README.md.

2010-07-15 20:18:39 -05:00

Makefile

Update C proxy to WS protocol version 76.

2010-06-30 20:39:41 -05:00

md5_test.c

Update C proxy to WS protocol version 76.

2010-06-30 20:39:41 -05:00

md5.c

Update C proxy to WS protocol version 76.

2010-06-30 20:39:41 -05:00

md5.h

Update C proxy to WS protocol version 76.

2010-06-30 20:39:41 -05:00

web.py

Move wsproxy and web utils into utils/ subdir.

2010-06-07 12:49:57 -05:00

websocket.c

Issue #11: daemonize after opening listen port.

2010-07-17 12:05:58 -05:00

websocket.h

Remove sequence code in client and proxies.

2010-07-01 12:13:17 -05:00

websocket.py

Issue #11: daemonize after opening listen port.

2010-07-17 12:05:58 -05:00

wsproxy.c

Issue #11: daemonize after opening listen port.

2010-07-17 12:05:58 -05:00

wsproxy.py

Issue #11: daemonize after opening listen port.

2010-07-17 12:05:58 -05:00