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 w3c/ServiceWorker#947 (comment) I had a discussion with @ricea and others about the merits of the WebSocket protocol in an H2 world. It seems that while this proposal tackles the single connection, it still leaves the frames (and therefore the messages) to be rather large.
Perhaps this is not a concern though as the motivation seems primarily to remove the need for servers to keep H1 code around, while being able to retain (legacy) WebSocket deployments.
The text was updated successfully, but these errors were encountered:
In w3c/ServiceWorker#947 (comment) I had a discussion with @ricea and others about the merits of the WebSocket protocol in an H2 world. It seems that while this proposal tackles the single connection, it still leaves the frames (and therefore the messages) to be rather large.
Perhaps this is not a concern though as the motivation seems primarily to remove the need for servers to keep H1 code around, while being able to retain (legacy) WebSocket deployments.
The text was updated successfully, but these errors were encountered: