Improve Documentation around Using Socket.IO with multiple nodes
@chill-cod3r is already working on this.
Since Nov 12, 2019.
Assessment
This issue has not been assessed yet.
Description
I would like to see the documentation expanded around the following:
It makes it sound like there being no fallback to polling is such a horrible thing, however I don't see a lot of concrete examples of what that means. Based on additional research, it seems to mean the following:
- won't support IE < 10
What else am i missing / what implications are there in terms of this? It also hints that if you don't care about polling you should use another library instead, but I don't feel like that's a solid reason, especially if you're already familiar with socket.io and how the middleware and connection authentication works.
There is also an additional part of the documentation that mentions "living dangerously" if you only use websocket transport, but again I don't feel like it explains why?
it mentions a socket connection failing due to a few reasons, however, what are other implications if any of this? What's wrong with requiring people to connect through the websocket protocol? How common is it (or at least give a more concrete example of a use case) that if you don't allow polling as a transport option a certain subset of people won't be able to use your app?
I'm opening this issue to have this discussion, learn the answer to my question, and then am 100% willing to update the documentation to provide more concrete examples of the points in question if that's acceptable.
Thanks!
- Dominant language
- JavaScript
- Stars
- 342
- Forks
- 1.1k
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from socketio/socket.io-website
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
socketio/socket.io-website#475 · 1 comment ·
-
The Replit and CodeSandbox interactive example links featured on the homepage under the "Basic example" section are currently broken and returning error pages.Possibly taken @Hashim1999164 claimed this 8 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 72/100
socketio/socket.io-website#551 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
socketio/socket.io-website#550 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 42/100
socketio/socket.io-website#539 · 7 comments ·
-
Step #7 Server delivery has multiple issuesPossibly taken @vipin8797 claimed this 124 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 38/100
socketio/socket.io-website#512 ·
All issues in socketio/socket.io-website
Similar issues
-
needs-website-changes
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 63/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
jaegertracing/jaeger-ui#4596 ·
Maintainers usually reply within 1 day
-
channels:add check:passed
Difficulty 1/5 Under an hour Newbie friendliness 72/100
Maintainers usually reply within 9 days