4 ms·
Agreed. This spec reads more like a brand new and complex transport protocol than an application one. Is it HTTP 2.0's plan to completely replace "middleware"
by meowface 13y ago
Agreed. This spec reads more like a brand new and complex transport protocol than an application one.
Is it HTTP 2.0's plan to completely replace "middleware" like SPDY with a full featured protocol?
- blueskin_ 13y agoYes, and about time too.
- rrmm 13y agoThe complexity is not horrible as far as communications protocols go. Anyone know what working implementations exist currently? Ideally, it'd be nice to see actual real world data showing the benefits over http 1.1.
- stephen_g 13y agoThere's a C++ implementation here, but I'm not sure how complete it is: https://github.com/http2d/core https://github.com/http2d/core I think nginx and Chrome support SPDY which HTTP 2.0 was based on, so that performance should be able to be tested and be fairly representative of what we can expect.
- jimktrains2 13y agoBut that's the thing...it's _not_ a communication's protocol. It's a transfer protocol...
- ll_cool_james 13y agoTo-may-to, to-mah-to..
- jimktrains2 13y agoNo, because a communication protocol has to handle all the types of problems HTTP and TCP solve. A transfer protocol is concerned with moving data and meta data, not the problems TCP solves.
- wmf 13y agohttps://github.com/http2/http2-spec/wiki/Implementations https://github.com/http2/http2-spec/wiki/Implementations
- thristian 13y agoHTTP 2.0 started with the SPDY spec and has been smoothed and refined during the IETF process, so yeah, it is planned to completely replace SPDY.
- mcguire 13y ago"Smoothed and refined" by the IETF?
- alanh 13y agoWhat are you seeking to clarify? Hard to tell if you are inquiring as to how that happened, quibbling with the word choices, or disagreeing completely.
- techdragon 13y agoLooks to me that it was an expression of 'quizzical sarcasm' in the form of a question.
- mcguire 13y agoI should probably have explained further, but there is a certain amount of irony in that statement. See ietf@ietf.org for more details: http://www.ietf.org/mail-archive/web/ietf/current/maillist.html http://www.ietf.org/mail-archive/web/ietf/current/maillist.h...
- rakoo 13y agoThe actual current of things is that HTTP 2.0 is what we want in the end, and SPDY is a toy to see what could be cool to add. When something that was tested with SPDY looks right, it is moved to the HTTP2 spec. I think the long-term goal is to deprecate SPDY in favor of HTTP2. This way of development is very interesting because it enables not only to change rapidly, but also to try completely new things on a different "namespace" (ie without polluting the whole HTTP stacke already deployed)