Iñaki Baz Castillo

Thanks for the explanation! Yes, I would find some text about this subject really useful in the API doc :)

I have no idea regarding what "wsf" is. I understand that it intends to be a message boundary protocol (in fact, the WebSocket protocol) over Unix Sockets in STREAM mode....

Well. I must say that this feature may be interesting. It still is "WebSocket", it's just that the transport is not TCP but named sockets. Node.js provides inter-process communication mechanisms,...

I fail to understand what changes in this PR fix the problem you mention in the PR description. So: 1. Can you please detail it a bit more? 2. Such...

I understand now, thanks. I'll approve this PR but I'm not the maintainer and cannot make a release. @theturtle32 any change to merge and release?

If Microsoft Edge 44.17763.1.0 uses Chromium, then there should be zero issues.

Not sure if the Node TCP API provides info regarding queued bytes and so on... I don't think so.

The [WebSocket API](https://html.spec.whatwg.org/multipage/web-sockets.html#network) (for browsers) does expose `ws.bufferedAmount`: > The `bufferedAmount` attribute must return the number of bytes of application data (UTF-8 text and binary data) that have been queued...

The only difference is that existing code may just react on `requestAccepted` or `requestRejected`, but I assume that if `requestClosed` is emitted the others would not. - Solution: Just behave...

I want to re-review this, sorry for the delay, off for many weeks.