[Ietf-caldav] Fwd: Summary of ETag related issues in RFC2518bis
helge.hess at opengroupware.org
Fri Dec 23 16:40:24 PST 2005
On 24. Dez 2005, at 01:31 Uhr, Mike Shaver wrote:
> On 12/22/05, Julian Reschke <julian.reschke at gmx.de> wrote:
>> Apache simply has decided that multiple updates within one second
>> semantically equivalent.
> Do you mean to indicate that such a decision on the part of Apache is
> reasonable, given the requirements of the HTTP specification? It
> certainly doesn't seem that way to me, but I am probably the biggest
> HTTP dullard on this list, so I'm happy to learn.
Maybe I'm wrong but if I understood Julian correctly Apache will
ensure that there will be only one PUT in the timeframe of 1s. If the
server ensures that, a timestamp with 1s granularity should be enough
for an etag?
More information about the Ietf-caldav