Re: [syndication] Re: RSS vs. HTML Bandwidth and "Scalability"...

[Mark Nottingham <mnot@mnot.net>]

More generally, it's caching.

The basic mechanisms are:
  - freshness: Expires and Cache-Control: max-age headers
  - validation: Last-Modified/If-Modified-Since and
    ETag/If-None-Match.

Browsers and intermediaries use these mechanisms. Friendly RSS
clients:
  - should cache locally, as allowed by RFC2616
  - should be able to be configured to use a caching proxy

There are more advanced mechanisms to do these things as well (CDNs,
invalidation protocols, push, etc.), but I'd recommend trying the
basics first, as the Web infrastructure offers them for free ;)

For more information, see 
  http://www.mnot.net/cache_docs/



On Thu, Aug 02, 2001 at 03:16:06PM -0500, Aaron Swartz wrote:
> On Thursday, August 2, 2001, at 03:07  PM, Morbus Iff wrote:
> 
> > What are your thoughts? Any additions to the above?
> 
> HTTP/1.1 has a solution to this, it's called If-Modified-Since. 
> If people are concerned about traffic, they should implement it.
> 
> --
> [ "Aaron Swartz" ; <mailto:me@aaronsw.com> ; <http://www.aaronsw.com/> ]
> 
>  
> 
> Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/ 
> 
> 

-- 
Mark Nottingham
http://www.mnot.net/