- From: Koen Holtman <koen@win.tue.nl>
- Date: Wed, 30 Jun 1999 19:03:21 +0200 (MET DST)
- To: connolly@w3.org (Dan Connolly)
- Cc: roconnor@uwaterloo.ca, www-talk@w3.org
Dan Connolly: > [...] >As a community, I feel we have the following choice: > -- provide TTL metadata in those cases where > we don't want clients (incl. proxy caches) > to assume a default TTL around a day or a week > or whatever, so that folks can implement caching per > the specs and get reasonable application behaviour > or > > -- live with the cache-busting techniques that providers > are forced into due to the current lack of discipline. ???? I'm confused, I don't follow how the above two choices are alternatives. Are the providers in your second alternative web content providers (the same people who must choose to generate explicit TTL metadata), or internet service providers who somehow bust the browser caches of their connected users to make things more transparent for them? The way I have seen it used, the term 'cache busting' always denotes techniques used by web content providers in order to disable caching which they think of as inappropriate for their content. >Dan Connolly, W3C Koen.
Received on Wednesday, 30 June 1999 13:03:29 UTC