New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Are "ping" and/or "pong" reserved events? #2414
Comments
I'm seeing strange behavior while using 'ping' / 'pong' event names - there does appear to be code in socket.io that does something with ping and pong, I don't have time to investigate further - changed name to 'drip' and 'drop' |
|
Just trapped by the 'ping' event for few hours. |
what a time waster. We all (including the socket.io team) had the same bad idea. So what ELSE is reserved? |
I have some basic code (see below) that works as expected when the events are named ding and dong but behaves very strangely when the events are named ping and pong
When the events are named ping and pong
Server Code
Client Code
I have no idea what is going on here. Also this may be related to #1951
The text was updated successfully, but these errors were encountered: