WebSockets #386

Closed
mnot opened this Issue Feb 15, 2014 · 9 comments

Projects

None yet

5 participants

@mnot
Member
mnot commented Feb 15, 2014

This issue is a placeholder / tracking issue for anything related to WebSockets support in HTTP/2.

@mnot
Member
mnot commented Feb 15, 2014

Note that our charter says we need to "will coordinate this item with...[t]he HYBI Working Group, regarding the possible future extension of HTTP/2.0 to carry WebSockets semantics."

@mnot
Member
mnot commented Jun 5, 2014

Discussed in NYC; we believe this could be done with extensibility (e.g,. with a new ALPN token, maybe new frame types + settings) - but we're not going to explicitly design it.

@mnot mnot closed this Jun 5, 2014
@thedrow
thedrow commented Jun 5, 2014

Why not? WebSockets are here to stay. If it won't be designed later implementations with HTTP 2.0 will be a mess (think JavaScript in the 90s).

@martinthomson
Member

@thedrow we haven't decided not to do websockets, we've only decided not to block HTTP/2 until a design for websockets over HTTP/2 is done.

@lenovouser lenovouser referenced this issue in mholt/caddy Sep 12, 2015
Closed

Disable HTTP2 for subdomain #189

@lenovouser

Are there any updates on this? It has been a whole year now since someone commented on this, are WebSockets still going to be implemented in HTTP/2?

Also see mholt/caddy#189

@MartinKei

What's the status on this one?

@martinthomson
Member

Awaiting someone to do some work: implement it, convince others to implement it, etc...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment