W3C home > Mailing lists > Public > public-appformats@w3.org > January 2008

Re: Examining the 'no server modification' requirement

From: Ian Hickson <ian@hixie.ch>
Date: Fri, 11 Jan 2008 11:06:50 +0000 (UTC)
To: Mark Nottingham <mnot@yahoo-inc.com>
Cc: Brad Porter <bwporter@yahoo.com>, "WAF WG (public)" <public-appformats@w3.org>
Message-ID: <Pine.LNX.4.62.0801111103120.13181@hixie.dreamhostps.com>

On Fri, 11 Jan 2008, Mark Nottingham wrote:
> 
> That's the beauty of the server-side model; it works very well with 
> caching.

Not as well as a purely static policy.


> E.g., if the request is
> 
> GET /foo HTTP/1.1
> Host: www.example.com
> Referer-Root: http://other.example.org/
> 
> The response could be
> 
> HTTP/1.1 200 OK
> Cache-Control: max-age=3600
> Vary: Referer-Root
> 
> ...
> 
> which tells a cache that it can serve that response to other clients, 
> *as long as* they send the same Referer-Root header.

The static policy system caches even better -- it isn't dependent on the 
Referer-Root header. This is of critical importance on low-bandwidth, 
high-latency systems like mobile devices.


  GET /foo HTTP/1.1
  Host: www.example.com
  Referer-Root: http://other.example.org/


  HTTP/1.1 200 OK
  Cache-Control: max-age=3600
  Access-Control: allow <*.example.org>

  ...

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 11 January 2008 11:06:58 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:56:21 UTC