Re:Turn any application that uses stdin/stdout into a WebSoc...
by wpears on Tuesday December 10, 2013 @01:19PM
(#6882490)
If the socket is terminated mid-command (thus emitting 'close'), one would want the process to be killed. Also, the socket doesn't know that no more transmission is required just because one particular stream is over. That is why close is called manually on the socket after the stream emits a 'close'.
This all provided you use a streaming web socket module like https://github.com/maxogden/websocket-stream
Re:Turn any application that uses stdin/stdout into a WebSoc...
by tlrobinson on Tuesday December 10, 2013 @01:11PM
(#6882422)
I thought about using pipe but the WebSocket library doesn't implement the Stream API, does it?
I still have a question for Node.js experts... would the 'close' events had to be handled then? Streams handle and propagate the 'end' event just fine, but should the underlying resource be closed? I guess killing `ps` is mandatory since ending `stdout` won't kill the process (or will it?), but is closing `ws` still mandatory too?