Re: Etag-on-write, 4rd attempt (== IETF draft 03), was: I-D ACTION:draft-reschke-http-etag-on-write-03.txt from Wilfredo Sánchez Vega on 2006-11-07 (ietf-http-wg@w3.org from October to December 2006)

From: Wilfredo Sánchez Vega <wsanchez@wsanchez.net>
Date: Tue, 7 Nov 2006 14:10:01 -0800
To: Helge Hess <helge.hess@opengroupware.org>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
Message-Id: <77AE5C1A-6CBE-403E-90CC-36EFDBE3EC85@wsanchez.net>

   It's not hard for a server to implement, but it's rather silly to  
invalidate caches for all resources when it shouldn't be necessary.

	-wsv

On Nov 6, 2006, at 3:08 PM, Helge Hess wrote:

> If the binary representation changes if the software changes, you  
> "just" need to embed a software version identifier in the etag? (eg  
> the iCal generation framework version [A/B/C...]) That doesn't sound  
> too hard / inappropriate.

Received on Tuesday, 7 November 2006 22:10:16 UTC