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
do not use events internally #171
Comments
I wrote a small failing test case for this |
Does this issue belong in engine.io-client? |
Yes |
Follow up: it seems like very little code depends on events internally in the client code: https://github.com/LearnBoost/engine.io-client/blob/master/lib/socket.js |
@brishin yeah, looks like 5 instances each of .on() and .once(). There's also an instance in lib/util.js and many more in the various lib/transports |
@davidhcummings Right, but there are only 3(?) instances of using the |
Faced with same issue. Because of this: https://github.com/socketio/engine.io/blob/master/lib/server.js#L334 |
Might be it makes sense to split internal events and events that developers could rely on ? |
Is this issue still relevant? |
like
once('close')
inserver.js
, since a user could callremoveAllListeners('close')
The text was updated successfully, but these errors were encountered: