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

Support HTTP/2 #184

Open
digitalextremist opened this Issue Mar 31, 2015 · 3 comments

Comments

Projects
None yet
2 participants
@digitalextremist
Member

digitalextremist commented Mar 31, 2015

We need to assess what we are not currently providing to make Reel::Server HTTP/2 compatible, then start to implement the missing pieces of what's needed to be able to accept HTTP/2 requests.

https://en.wikipedia.org/wiki/HTTP/2#Differences_from_HTTP_1.1

We don't seem that far off from compliance, especially with the core theory involved in pipelining in place.

@digitalextremist digitalextremist added this to the 0.7.0 milestone Mar 31, 2015

@digitalextremist

This comment has been minimized.

Show comment
Hide comment
@digitalextremist

digitalextremist Mar 31, 2015

Member

It seems like the majority of this will invoke server push mechanics, which may be a tad more involved than Reel itself can handle by its limited scope. It doesn't know much about the context it is serving in.

This might become a separate reel-http2 gem, with a configuration object API to describe for the server what resources it can push to the client. That is, if HTTP/2 is largely about server context awareness.

Member

digitalextremist commented Mar 31, 2015

It seems like the majority of this will invoke server push mechanics, which may be a tad more involved than Reel itself can handle by its limited scope. It doesn't know much about the context it is serving in.

This might become a separate reel-http2 gem, with a configuration object API to describe for the server what resources it can push to the client. That is, if HTTP/2 is largely about server context awareness.

@digitalextremist

This comment has been minimized.

Show comment
Hide comment
@digitalextremist

digitalextremist Mar 31, 2015

Member

Encryption out-of-the box also seems like a core requirement of HTTP/2.

Member

digitalextremist commented Mar 31, 2015

Encryption out-of-the box also seems like a core requirement of HTTP/2.

@digitalextremist digitalextremist modified the milestones: 0.7.0, 1.0 Feb 16, 2016

@kenichi

This comment has been minimized.

Show comment
Hide comment
@kenichi

kenichi Sep 1, 2017

Member

see #242

Member

kenichi commented Sep 1, 2017

see #242

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