Hacker News new | past | comments | ask | show | jobs | submit login

A project in a similar vein is websockify ( https://github.com/kanaka/websockify ) , which makes an existing app with a TCP endpoint available over websockets.



What are the differences? Do I miss anything?

1. websocketify allows binary, while websocketd is text-only

2. websocketify does I/O through a socket that the program uses (and that it sniffes through rebind.so), while websocketd relies on stdin / stdout

3. The arguments are different

websocketd --port=8080 my-program

websocketify 8080 -D -- my-program


Also websocketd is multiplatform and does not require python. Neither good or bad, just another difference :)

Also, not sure if websocketify can but websocketd also has --dir argument and can supervise and route many sockets to many different programs.


websockify can be run on Node.js as well as python. Both versions seem to be highly reliable (I'm using them on multiple production servers with paying customers for web conferencing). The python version doesn't seem to work on Windows servers, but the Node version works fine.


I haven't used websocketify. I'd be interested to have users try out both and write up their experiences.


Nice! I hadn't seen that. Yeah, that's pretty sweet.




Guidelines | FAQ | Support | API | Security | Lists | Bookmarklet | Legal | Apply to YC | Contact

Search: