You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the WebSockets page, MessageWebSocket is described as being "similar to a UDP to datagram socket". I find that claim surprising, since it literally it is built on top of TCP.
I understand that the goal of that table is to point that it is intended for frequent, small messages, as opposed to StreamWebSocket, but maybe there is a less confusing way to word it? Readers who are not familiar with the WebSocket protocol might understand (incorrectly) that the MessageWebSocket is not reliable, does not guarantee same order reception or does not include congestion control.
The text was updated successfully, but these errors were encountered:
In the WebSockets page, MessageWebSocket is described as being "similar to a UDP to datagram socket". I find that claim surprising, since it literally it is built on top of TCP.
I understand that the goal of that table is to point that it is intended for frequent, small messages, as opposed to StreamWebSocket, but maybe there is a less confusing way to word it? Readers who are not familiar with the WebSocket protocol might understand (incorrectly) that the MessageWebSocket is not reliable, does not guarantee same order reception or does not include congestion control.
The text was updated successfully, but these errors were encountered: