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: 陈智昌 <willchan@chromium.org>
Date: Thu, 24 Jan 2013 16:57:13 -0800
Message-ID: <CAA4WUYj5V9keihyCCcTbBthpcYXuO21UzcQAhFtQZ+FWDcKxaQ@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>, Nico Williams <nico@cryptonector.com>, HTTP Working Group <ietf-http-wg@w3.org>
After reading Nico's reply, I realize I misunderstood your email.
Ignore my previous email.

On Thu, Jan 24, 2013 at 4:49 PM, William Chan (陈智昌)
<willchan@chromium.org> wrote:
> http://lists.w3.org/Archives/Public/ietf-http-wg/2013JanMar/0357.html
>
> On Thu, Jan 24, 2013 at 4: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?
>>
>>
>> Robert Brewer
>> fumanchu@aminus.org
Received on Friday, 25 January 2013 00:57:40 GMT

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