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

Re: Implementation Notes on Server Push

From: Patrick McManus <pmcmanus@mozilla.com>
Date: Wed, 15 May 2013 17:59:56 -0400
Message-ID: <CAOdDvNpU7ZRGy29z+SYi=rexMPzaYx5CcSN+faitfRGVjQosjw@mail.gmail.com>
To: William Chan (陈智昌) <willchan@chromium.org>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
On Wed, May 15, 2013 at 5:41 PM, William Chan (陈智昌)
<willchan@chromium.org>wrote:

>
>> Its a particular quandary on mobile. The RTT is certainly costlier.. but
>> storage is costlier too and more importantly to me the data transfer can be
>> exceptionally expensive.
>>
>
> When you say storage, do you mean memory or disk?
>

could be either, or both. depending on deployment.



> What do you think about SETTINGS_MAX_CONCURRENT_STREAMS vs flow control
> here?
>

deserves experimentation.. though flow control seems more fine grained to
me.


> Also, when you say an established sink, how about the browser cache?
>

For a pretty significant set of deployments I would rather wait 1 rtt than
deal with storage i/o :)
Received on Wednesday, 15 May 2013 22:00:23 UTC

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