Talk:WebSocket
This is not a forum for general discussion of the subject of the article.
- Put new text under old text. Click here to start a new topic.
- New to Wikipedia? Welcome! Learn to edit; get help.
- Assume good faith
- Be polite and avoid personal attacks
- Be welcoming to newcomers
- Seek dispute resolution if needed
It is of interest to the following WikiProjects:
icon To-do list for WebSocket: edit · history · watch · refresh · Updated 2025年08月28日
- Add "Backpressure problem" subsection to "Web API" section. Include proposed standardization of WebSocketStream.
- Add section explaining deflate extension.
NAT
[edit ]Most computers have a NAT address. Websocket seems to work at public IP addresses but not when the server is behind NAT with port forwarding, which does work with http servers behind NAT. — Preceding unsigned comment added by 75.130.143.161 (talk) 17:04, 28 March 2020 (UTC) [reply ]
- When you say it does not work, do you mean it does not work at all, ever, to do a WebSocket connection to a server behind a NAT, or that the connection stops working after awhile? — Preceding unsigned comment added by 82.99.11.116 (talk) 12:01, 4 March 2021 (UTC) [reply ]
Remove historical info like drafts-info and their proxy problems, or at least move it to a Historical chapter?
[edit ]The standard was set in 2011, that is, 10 years ago. To high light which implementations support pre-standard drafts must be of extremely low value from 2021 and onwards and only clutters the page. Discussions about so old pre-standard draft versions and their problems and changes vs the established standard is of course information in itself, but shouldn't a general Wikipedia page about WebSocket protocol skip such old unimportant historic aspects given that the standard is 10 years old and stable since long?
There is also a part in the Proxy Chapter discussing problems with draft implementations which could be removed. It probably only complicates understanding more than it actually explains — Preceding unsigned comment added by 82.99.11.116 (talk) 11:53, 4 March 2021 (UTC) [reply ]
Add simple implementation inline (e.g. Python)
[edit ]I believe the WebSocket protocol is not too complicated, which means it shouldn't be too bad to add a full implementation in, let's say, Python.
I'm not sure to what extent or how broad it should be.
I think two simple client and server code blocks should suffice. Dewycube (talk) 00:09, 9 April 2024 (UTC) [reply ]
Change opcode text
[edit ]In the Opcodes table we say:
> The payload is optional, but if present, it must start with a two-byte big-endian unsigned integer reason code,
The "reason code" later is referred to as Status codes. It's not always easy to mentally connect "reason code" with "status code". The spec uses the term status code. I suggest changing the text to something like "it must start with a two-byte big-endian unsigned integer status code". Bibhas22 (talk) 16:44, 7 January 2025 (UTC) [reply ]
- No objection from me. Go ahead and make the edit yourself if you want. –Novem Linguae (talk) 16:53, 7 January 2025 (UTC) [reply ]
- I support your suggestion. It has been a few months since your comment, so I changed it myself. Connoisseurship (talk) 14:48, 2 May 2025 (UTC) [reply ]
- C-Class Computing articles
- Mid-importance Computing articles
- C-Class Computer networking articles
- Mid-importance Computer networking articles
- C-Class Computer networking articles of Mid-importance
- All Computer networking articles
- C-Class Websites articles
- Mid-importance Websites articles
- C-Class Websites articles of Mid-importance
- All Websites articles
- All Computing articles
- Wikipedia pages with to-do lists