Blog post: A Proposal: Multiple Request-URIs in HTTP/2 bit.ly/10IqGIn
1
1
2
@jasnell Seems like a great idea for HTTP 2.0, but I don't see how this could be made semantically compatible with HTTP 1.1
2
@stilkov into two separate requests with identical header sets. the response streams are separate and identical in either case.
1
Replying to @jasnell
@jasnell Not sure my point is clear: I meant it will be hard to write an HTTP client lib that hides this. May not be a goal, though.

Mar 12, 2013 · 5:03 PM UTC

2
Replying to @stilkov
@stilkov for those that want transparent http/1 and /2 support, they can ignore this really. a client could choose not to send multiples
Replying to @stilkov
@stilkov so for devs who want to write a clientlib that keeps all http/1 semantics and just use /2 just as new transport they can do so