On 12/3/05, Julian Reschke <julian.reschke@gmx.de> wrote:
> Hi,
>
> sorry for being late in the discussion.
>
> I just remembered that there actually may be a good reason for not
> returning Last-Modified dates. This is because this response header must
> work properly per URL, not per resource, and thus names pace operations
> (such as MOVE) need to be taken in account (see
> <http://greenbytes.de/tech/webdav/draft-reschke-webdav-namespace-vs-properties-latest.html>
> for a longer summary).
>
> That is, if you have
>
> /a/b (with Last-Modified of 10am)
>
> and
>
> /a/c (with Last-Modified of 11am)
>
> moving /a/b to /a/c *must* result in /a/c having a Last-Modified of
> later than 11am (thus the underlying resource can't keep it's timestamp
> here).
If I understand correctly, the timestamp returned is the one of the
time the commit took place (ie the time of the MOVE operation). That
would satisfy this requirement.
> Maybe this is already the case (in which case I apologize for raising a
> non-issue).
Not at all! Thanks for bringing up these potential problems!
bye,
Erik.
Received on Sat Dec 3 11:51:53 2005