HTTP v2 commit out-of-dateness checks
From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Mon, 23 Feb 2009 15:56:22 -0500
I started down the path of adding If: headers to the ra_serf commit-related
http://subversion.tigris.org/issues/show_bug.cgi?id=1017#desc11
Are Ben's comments about the problems with using etags and If: accurate? Do
When I posed a question about why to use If: and etags instead of a custom
A: Because If-Match is standard HTTP, and proxies can/should
Just jam that base-revision into the etag. In fact, I think
I'm not sure I understand the benefit with respect to proxies here, though.
"REV/path/to/item" ### etag
but the client doesn't pass that format back to the server in its If:
</path/to/item> (<LOCK-TOKEN>) ### used for verifying locks
and uses the custom X-SVN-Version-Name: header to transmit base revisions.
Help?
-- C. Michael Pilato
-- C. Michael Pilato <cmpilato_at_collab.net> CollabNet <> www.collab.net <> Distributed Development On Demand ------------------------------------------------------ http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1216601
|
This is an archived mail posted to the Subversion Dev mailing list.
This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.