Re: protocol/4197: FYI - inodes in etags will not be the same in _replicated_ content.

[dg...@apache.org]

[In order for any reply to be added to the PR database, ]
[you need to include <ap...@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[automatically because of the potential for mail loops. ]
[If you do not include this Cc, your reply may be ig-   ]
[nored unless you are responding to an explicit request ]
[from a developer.                                      ]
[Reply only with text; DO NOT SEND ATTACHMENTS!         ]


Synopsis: FYI - inodes in etags will not be the same in _replicated_ content.

State-Changed-From-To: open-closed
State-Changed-By: dgaudet
State-Changed-When: Tue Apr 20 11:30:33 PDT 1999
State-Changed-Why:
Yeah but the joy of etags is that you can collect as many as
you want... and they're tied to the resource (uri) they came
from.

If two "generations" of a URI map to the same inode there's
always the mtime to distinguish the two.  If two identical
copies of the file exist on two servers with differing etags
then the reverse proxy will just end up with a few choices
for the file... it means it'll be transferred more than once...
but oh well.  If you're using a reverse proxy you can just
disable etag comparison -- it is a local decision after all.

Dean
Category-Changed-From-To: general-protocol
Category-Changed-By: dgaudet
Category-Changed-When: Tue Apr 20 11:30:33 PDT 1999