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: Nico Williams <nico@cryptonector.com>
Date: Thu, 24 Jan 2013 18:53:12 -0600
Message-ID: <CAK3OfOiOeKUAVugVk7pKDwx+-bOiS-hbQ0hZxZaKjydniOuz=A@mail.gmail.com>
To: Robert Brewer <fumanchu@aminus.org>
Cc: Roberto Peon <grmocg@gmail.com>, Phillip Hallam-Baker <hallam@gmail.com>, Yoav Nir <ynir@checkpoint.com>, ietf-http-wg@w3.org
On Thu, Jan 24, 2013 at 6:44 PM, Robert Brewer <fumanchu@aminus.org> wrote:
> Roberto Peon wrote:
>> The worst part is the high latency, especially given TCP's
>> current cogestion avoidance implementations-- the total number
>> of round-trips ends up dominating latency, regardless of how
>> much bandwidth one has.
>
> Why is this being addressed by trying to make the messages smaller? Wouldn't following the original architecture of HTTP, which was optimized for fewer, larger messages, also reduce latency?

This would require significant changes to HTML and web services.
HTTP/2.0 would be a much more transparent change.

Nico
--
Received on Friday, 25 January 2013 00:53:37 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 25 January 2013 00:53:40 GMT