Brian McKelvey
Brian McKelvey
To clarify, are you saying that when you send a large amount of data to the remote peer, it can take so long just to send the ping that the...
Currently, we do reset the keepalive timeout every time we receive incoming data of any sort, which seems to cover most cases, but I suppose it is plausible that the...
I wonder if I should switch the default to be TCP keepalive instead, at this point?
Ok. As for your approach, unsolicited pong frames are explicitly allowed in the WebSocket RFC, so there's no protocol violation.
Another possible approach would be to maintain our own buffer of outgoing packets and pay attention to the backpressure on the socket, so that we can allow certain control frames...
> Am I right to determine my current websocket version by looking at the first lines of CHANGELOG.md and README.md? I must clarify this important point as I am afraid...
Try pushing your connection in the request handler, not the message handler.
To be entirely honest, I'm not quite sure I'm following what you're reporting here?
Using your test code between my machine and a remote server, I'm not able to reproduce any problem with the current release version of WebSocket-Node.