Eliot, On Dec 18, 2013, at 3:00 AM, Eliot Lear <lear@cisco.com> wrote: > ... >> I.e., we're not required to make HTTP/2 a replacement for HTTP/1 *in the market*, as such; only to make the specs suitable for it. > > To answer your other question and the charter, since you went there, I > don't really see a net benefit for most non-browser uses. We've limited From a resource perspective alone I think multiplexing requests over a single connection is a major win for any HTTP-based RPC protocol (IPP, SOAP, REST, etc.) where you expect to send or receive more than one message. _________________________________________________________ Michael Sweet, Senior Printing System Engineer, PWG Chair
Received on Wednesday, 18 December 2013 15:32:41 UTC