W3C home > Mailing lists > Public > ietf-http-wg@w3.org > October to December 2011

Re: Negotiated private cache storage allocation

From: Mike Kelly <mike@mykanjo.co.uk>
Date: Wed, 14 Dec 2011 21:55:37 +0000
Message-ID: <CANqiZJap5ZaJMhHtuMZzXt9dM3mG1rwQeqO1KGu6ptkYKzSyPg@mail.gmail.com>
To: Amos Jeffries <squid3@treenet.co.nz>
Cc: ietf-http-wg@w3.org
I think the negotiation process could, and should, allow for UAs (e.g.
browsers) to consult with a user before making the allocation. No?

On Wed, Dec 14, 2011 at 8:08 PM, Amos Jeffries <squid3@treenet.co.nz> wrote:
> On Wed, 14 Dec 2011 20:16:16 +0000, Mike Kelly wrote:
>>
>> Hi,
>>
>> Is anyone aware of any proposals that extend HTTP to allow servers and
>> clients to negotiate client-side storage allocation for client-side
>> (private) caches?
>>
>> Basically, I'm looking for a way for a server to indicate how much
>> storage should be allocated for caching responses from a particular
>> domain name, and possibly also for the client to be able to indicate
>> how much allocation was actually possible.
>>
>> Aside from that, if you have any thoughts on whether or not this is
>> really feasible or is just a plain bad idea - please let me know
>>
>> Thanks,
>> Mike
>
>
>
> Can you explain why this is needed please? It seems to be something the
> browser agents should be allocating dynamically internally instead of
> pre-allocating blocks of wasted space.
>
> For an example; I can just imagine sites like SourceForge negotiating a few
> dozen GB to be allocated then deallocated for a visitor, who only hits once
> on a 20KB page, simply because it allows code repository browsing with huge
> memory requirements elsewhere on the site.
>
> AYJ
>
>
Received on Wednesday, 14 December 2011 21:56:09 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:51:51 GMT