Make Socket.IO great again
See original GitHub issue(yep, that headline is overrused)
Disclaimer:
- I have no control over the website (socket.io), to my knowledge only @rauchg has, so I’m unfortunately not able to fix those issues: https://github.com/socketio/socket.io/issues/2807 https://github.com/socketio/socket.io/issues/2791 https://github.com/socketio/socket.io/issues/2781 https://github.com/socketio/socket.io/issues/2773 https://github.com/socketio/socket.io/issues/2753 https://github.com/socketio/socket.io/issues/2743 https://github.com/socketio/socket.io/issues/2736
- I have no control over the chat example repository, that is the one that is behind the chat example, so I’m unfortunately not able to fix those issues: https://github.com/socketio/socket.io/issues/2821 (and all open PR over there)
- I’m not even an expert in Socket.IO, just a developer digging around during his free time between two freelance contracts
Now, enough about my limitations. The Server API and Client API were added on Github, do not hesitate if you find something missing!
Current to-do list:
- release the version
2.0
of Engine.IO Engine.IO will now default to uws as WebSocket engine, that should bring great performance improvements. An important issue about double UTF-8 encoding was also fixed in the parser. The only “problem” is that one of the numerous issues open could need a fix over there, hence the delay. - complete the API docs (missing methods, code examples…): https://github.com/socketio/socket.io/issues/2350#issuecomment-209575927
- add a
Features
section in the README, listing all features provided by Socket.IO (reconnection, multiplexing, rooms…) - add an
Architecture overview
section, listing every project (socket.io-adapter
,socket.io-parser
…) and maybe describing what’s happening behind the hood when callingsocket.emit()
orio.emit()
. - take control over the website and the online examples. @rauchg suggested to rewrite the website with next.js (currently it is backed by WordPress) and to host it at https://now.sh
- merge the cluster examples: nginx, haproxy, httpd, reviews are welcome!
- merge the whiteboard example: https://github.com/socketio/socket.io/pull/2810
- dig into CORS issue: https://github.com/socketio/engine.io/issues/279 > https://github.com/socketio/engine.io/pull/491
- dig into binary performance issue: https://github.com/socketio/socket.io-parser/issues/61
- maybe update the Namespace API on the client-side (https://github.com/socketio/socket.io-client/issues/1029, https://www.rabbitmq.com/blog/2012/02/23/how-to-compose-apps-using-websockets/)
- add a Webpack build example: https://github.com/socketio/socket.io/issues/2109 > https://github.com/socketio/socket.io/pull/2828
- dig into handshake optimisation: https://github.com/socketio/socket.io/issues/1954 (somewhere around here) > https://github.com/socketio/engine.io/pull/471
- dig into custom codecs: https://github.com/socketio/socket.io/issues/1946
- document the slim build: https://github.com/socketio/socket.io-client/pull/1030 (related: https://github.com/socketio/socket.io/issues/2610)
- fix the id generation on the client-side: https://github.com/socketio/socket.io-client/pull/1058
I closed quite a lot of issues yesterday through the GitHub API (hitting the rate limit several times), in order to have some feedback (like this one ❤️) and to be able to focus to the active ones.
As usual, every contribution is welcome!
Issue Analytics
- State:
- Created 7 years ago
- Reactions:100
- Comments:24 (10 by maintainers)
Top Results From Across the Web
Performance tuning - Socket.IO
Here are some tips to improve the performance of your Socket.IO server:
Read more >Migrating from 3.x to 4.0 - Socket.IO
The new value (20s) thus seems like a good balance between quick disconnection detection and tolerance to various delays.
Read more >Migrating from 2.x to 3.0 - Socket.IO
This release should fix most of the inconsistencies of the Socket.IO library and provide a more intuitive behavior for.
Read more >Using multiple nodes | Socket.IO
When deploying multiple Socket.IO servers, there are two things to take care of:
Read more >Application structure | Socket.IO
socket.on("order:create", createOrder); ... which is great for discoverability, but could get out of hand in a medium/big application.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
May the force with you.
My hope is to support you and help out with the website. As soon as we add organizations support to now.sh I’ll be able to include you. In the mean time, feel free to point me to what repositories I should deploy at what URLs!
On Fri, Jan 13, 2017 at 1:55 AM Damien Arrachequesne < notifications@github.com> wrote: