W3C home > Mailing lists > Public > ietf-http-wg@w3.org > April to June 2014

Re: Negotiating compression

From: Johnny Graettinger <jgraettinger@chromium.org>
Date: Wed, 28 May 2014 11:58:21 -0400
Message-ID: <CAEn92TocyJMgF2fnse_Ayz18TZs8xwH535zfQ+388nj_BTnN9A@mail.gmail.com>
To: Michael Sweet <msweet@apple.com>
Cc: Eliot Lear <lear@cisco.com>, "Richard Wheeldon (rwheeldo)" <rwheeldo@cisco.com>, Nicholas Hurley <hurley@todesschaf.org>, Martin Thomson <martin.thomson@gmail.com>, HTTP Working Group <ietf-http-wg@w3.org>
>
> (and in case you are wondering, yes they do TLS with 16-bit processors, it
> just works slowly...)
>

The only real difference between IPP and a typical web page load is the
> sheer volume of data - gigabytes for a raster printer versus megabytes for
> a typical web page without video (you'll get gigabytes for HD video).
>


Forgive me as IANAE, but isn't the bit-manipulation cost from
Huffman-decoding small meta-data blocks on a stream, overwhelmed by the
cost of transferring gigabytes of data on that same stream over a TLS link?




>
> Rather than claiming that HTTP was never designed to support such usage
> after the fact, perhaps it would be more constructive to accept that HTTP
> *is* used for things not directly connected to a web browser or web page.
>  I will also point out that all versions of the HTTP specs going back to
> RFC 1945 (HTTP/1.0) talk about HTTP being used for more than just web
> browsers.  Developers didn't just decide to subvert HTTP, *they were given
> permission and encouraged to use HTTP as a generic communication protocol*.
>
> _________________________________________________________
> Michael Sweet, Senior Printing System Engineer, PWG Chair
>
>
Received on Wednesday, 28 May 2014 15:58:49 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:30 UTC