W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2013

Re: Should Web Services be served by a different HTTP n+1?

From: Julian Reschke <julian.reschke@gmx.de>
Date: Thu, 24 Jan 2013 16:40:19 +0100
Message-ID: <510155E3.5020208@gmx.de>
To: Phillip Hallam-Baker <hallam@gmail.com>
CC: Greg Wilkins <gregw@intalio.com>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>
On 2013-01-24 16:20, Phillip Hallam-Baker wrote:
> If people don't want there to be two different families then I think the
> header compression needs to be totally rethunk.
>
> I do not want to have a compression library in my Web Services. Too much
> code bloat and more importantly, too much memory overhead and too much CPU.
>
> If we want to have a single protocol then maybe what we should be
> thinking of is using the coap codes as the starting point for header
> tokenization.
> ...

As a matter of fact, figuring out the header field serialization is one 
of the current HTTP/2 related topics the WG discusses. See the various 
proposals and test suites.

Best regards, Julian
Received on Thursday, 24 January 2013 15:40:53 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 24 January 2013 15:40:55 GMT