Roadmap for v3
See original GitHub issueThis list is open to suggestions!
- Improve the documentation
That is obviously the major pain point of the project.
- Reverse the direction of the ping-pong mechanism
Currently the client emits a ping
and waits for a pong
from the server, relying on setTimeout()
to check whether the connection is still alive or not. But there are reports of throttled timers on the browser side, which may trigger random disconnections.
A solution would be that the ping
is emitted from the server to the client, but that is a breaking change which will also break other client implementations…
Related: https://github.com/socketio/engine.io/issues/312
-
Update the source code to ES6 in every project
-
Migrate to webpack 4 (or another bundler, if need be)
-
Remove the sticky-session requirement when using multiple nodes
-
Default to websocket, and use XHR polling as fallback
Currently polling is established first, and then upgraded to websocket if possible.
- Make the
generateId
method asynchronous
This one is also a breaking change. Related: https://github.com/socketio/engine.io/pull/535
-
Update the Typescript bindings, if need be
-
Triage issues
No release date for now, as I’m not sure how much time I will be able to dedicate to those points in the following weeks. But any help is welcome!
Issue Analytics
- State:
- Created 5 years ago
- Reactions:11
- Comments:51 (22 by maintainers)
Top GitHub Comments
We’ve already released Engine.IO v4, which will be included in Socket.IO v3. You can find the release notes here.
I’ve added what I could find in this thread to the project here, to give an overview of the progress. Do not hesitate to comment!
socket.io@3.0.0-rc1
andsocket.io-client@3.0.0-rc1
have been published 🔥A few notes:
Any feedback is welcome!