Closed princjef closed 7 years ago
Thanks for that one too! I'm still wondering about the Babel thing, but I need to find some time to checkout your PR and see what's going on.
@jbmusso Do you have an update on this and other PRs that are waiting? Is there anything that I (or someone else) can help with in testing or reviewing them?
It's all good to me!
After 48h of live test on a production website, it appears that the new module version (that includes this PR merged) makes my application no longer randomly crash. Thanks a lot guys, really. Florent
Thanks for the feedback @dragma, appreciate that it's running fine!
Addresses the issue in #67 by emitting a warning message whenever a message is received on the socket with no associated request
messageStream
to handle it. Also handles malformed message payloads.A comment on design: While there is an error underlying this message, it doesn't have the same ramifications as a standard error that is emitted when the client connection has a problem. For one, it shouldn't close the connection. On top of that, if a client doesn't listen for
'error'
node will throw. I'm open to using something other than'warning'
, but I'd rather not use'error'
for these reasons.