Show HN: A Unixy approach to WebSockets

Re:Show HN: A Unixy approach to WebSockets by espadrine on Saturday February 14, 2015 @06:14PM (#9051089)

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

[ Parent | on HN ]

Re:Show HN: A Unixy approach to WebSockets by asergeyev on Saturday February 14, 2015 @06:56PM (#9051205)

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.

[ Parent | on HN ]

Re:Show HN: A Unixy approach to WebSockets by cpncrunch on Sunday February 15, 2015 @11:52AM (#9053121)

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.

[ Parent | on HN ]

Re:Show HN: A Unixy approach to WebSockets by joewalnes on Saturday February 14, 2015 @06:17PM (#9051099)

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

[ Parent | on HN ]