Talk:WebSocket

This is the talk page for discussing improvements to the WebSocket article.
This is not a forum for general discussion of the article's subject.

Put new text under old text. Click here to start a new topic.
New to Wikipedia? Welcome! Learn to edit; get help.

Article policies

Find sources: Google (books · news · scholar · free images · WP refs) · FENS · JSTOR · TWL

Archives: 1: 3 months

Computing: Networking / Websites Mid‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Mid	This article has been rated as Mid-importance on the project's importance scale.
	This article is supported by Networking task force (assessed as Mid-importance).
	This article is supported by WikiProject Websites (assessed as Mid-importance).

NAT

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]

WebSocket vs WebSockets, part II

While this has already been debated, I feel like we should at least mention the plural vs singular differentiation and usage in the article (along with an assertion of which being correct). Personally, I landed on this page trying to figure out which was more correct. I don't have the answer on it, but I think that it would be an interesting section to have. — Preceding unsigned comment added by Meow-ology (talk • contribs) 20:34, 19 August 2020 (UTC)[reply]

Remove historical info like drafts-info and their proxy problems, or at least move it to a Historical chapter?

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)

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]