Stream-like websock.js

[ishitatsuyuki]

To maximize Node.js socket based application's portability to browser, I would like to see an identical interface between sockets. The current websock.js interface is somewhat messed up, and I think it's sufficient to only expose the traditional read-write interface only instead of the complicated queues, as the other end would be using websockify proxy and it's nothing more than a classic socket.

There's a reference implementation for the sockets interface itself, and we should be possible to implement it with minimal effort.

[kanaka]

I can't speak for the rest of the team, but I we would be happy to consider a Streams API implementation that people could use as an alternate browser interface (i.e. choose websock.js or streams.js) to communicate with websockify.

@ishitatsuyuki are you planning to implement this? I don't think anybody on the team has the time or use-case for this so it would need to come from outside the team.

[ishitatsuyuki]

I'm willing to do this, although it may take some time. Thanks for your information.

[jimmywarting]

whatwg streams for frontend and node streams for backend?