> What are your thoughts on whether the charter does and/or should include
> either or both of the following ideas.
>
> 1. Lease-based caching: there can be a contract between a client and a server
> (some caching proxies, at least, and perhaps also origin servers), in which
> the server is responsible for notifying the client when pages fetched by
> the client cease to be the latest version.
Yes, I think it should be in the charter. I also think it should apply
to all caches - a cache should always tell an origin server
"I'm going to cache this" and an origin server should always be able
to tell the cache "don't cache this"... or at any later time the
origin server should be able to contact the cache and say
"your cached copy of this page is now invalid"
(and optionally... "here's a more recent copy of that page")
> 2. Replicated servers: rather than "an origin server", there is a collection
> of peer origin servers; a given client (user agent or intermediary) reads
> from and writes to a single one of the peers, and the peers propagate the
> updates among themselves.
yes, this should also be in the charter. though the origin servers need
not be "peers", nor do we need to assume a master/slave update scheme.
Keith
This archive was generated by hypermail 2b29 : Thu Nov 18 2004 - 11:21:25 MST