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. `._.-(,_..'--(,_..'`-.;.'
