>
> MT> Given that, do we want to require containers to support h2c?
>
> While browsers do represent the bulk of software interacting with
> Servlet implementations, they are not the only ones. Stuart, where do
> you come by your assertion that browsers are not going to implement
> HTTP/2 over upgrade?
>
So looks like I mis-remembered, Chrome and Firefox will not implement h2c, while IE will (although AFAIK have not as yet)
Chrome:
http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/0676.html
Firefox (I can't find the email where the definitively state that, but it is referenced in passing in a lot of the WG emails):
http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/0987.html
IE:
http://lists.w3.org/Archives/Public/ietf-http-wg/2013OctDec/0662.html
For what its worth I think we should support h2c in servlet, both via upgrade and prior knowledge. Even if browsers don't end up supporting it there will likely be plenty of use cases where it is useful (e.g. at the moment AJP is widely used to connect a load balancer to backend servers, in time to come I can see h2c filling this role instead).
Stuart