Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Frame overhead #1

Closed
annevk opened this issue Oct 16, 2017 · 1 comment
Closed

Frame overhead #1

annevk opened this issue Oct 16, 2017 · 1 comment

Comments

@annevk
Copy link

annevk commented Oct 16, 2017

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.

@mcmanus
Copy link
Owner

mcmanus commented Oct 16, 2017

You're right about the scope - this is just meant to be a shim rather than a rethinking. hopefully https://github.com/mcmanus/draft-h2ws/blob/master/README.md catches some of that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants
@mcmanus @annevk and others