Re: #385: HTTP2 Upgrade / Negotiation

On Tue, Oct 23, 2012 at 7:29 PM, Roberto Peon <grmocg@gmail.com> wrote:

> [snip]
> > Also, how would one go about re-writing the entire legacy web page set
> to use http2:// URLs when the server (or even just its frontend proxy!)
> upgrades?
>
> As I understand the suggestion, that want required. What I understood was
> that a scheme of http2 meant one should assume you can use HTTP/2. An HTTP
> scheme , however didn't mean only http/1.x-- it could also be http/2 after
> negotiations.
>
Yep. http2:// would mean skip the negotiation.

>  Proxies make any of this moot, however, if they are used-- a negotiation
> must happen if there is ever anything other than direct connectivity. If
> the scheme is just used as a hint instead of an assertion (I.e. one can
> always fall back to 1.1) it is technically useful in potentially , maybe,
> saving an rtt... but ugly and it could end up costing more in the case
> where a proxy doesn't understand http/2 and where the session must be
> restarted...
>
>
> The point of the http2 scheme is that backwards compatibility with
http/1.1 infrastructure is not always going to be requirement. I'm not
arguing that it should be used for all cases... just in the subset of cases
where explicitly skipping negotiation makes sense. For example, if I have a
media server running on my local home wireless network and I have a
dedicated client app for that on my mobile device connected to the same
wireless network. There is no proxy between the two devices, just a direct
connection between a client app and a server app. There's no reason at all
why upgrade negotiation would be required in this case. A client stack on
the mobile device could be given a url.. http2://10.0.0.2/movies and just
know that http/2 is to be used.

One thing that needs to be recognized is that there will not be a single
solution that's going to work for all cases.

- James