On Mon, 13 Dec 2004 sussman@tigris.org wrote:
> Author: sussman
> Date: Mon Dec 13 16:29:44 2004
> New Revision: 12304
>
> Added: trunk/notes/locking/ra_dav_strategy.txt
> Url: http://svn.collab.net/viewcvs/svn/trunk/notes/locking/ra_dav_strategy.txt?view=auto&rev=12304
> ==============================================================================
> --- (empty file)
> +++ trunk/notes/locking/ra_dav_strategy.txt Mon Dec 13 16:29:44 2004
> @@ -0,0 +1,89 @@
> + How we will extend ra_dav/mod_dav_svn protocol for locking feature
> + ==================================================================
> +
> +
> +RA->unlock()
> +
> + * send http UNLOCK request with 1 custom header:
> +
> + - force flag
> +
> + * mod_dav_svn should call authz_read func on path, if it exists.
> +
> + * generate http UNLOCK response: success == "204 no content"
> +
> + - has one custom response header: creation-date
> +
What's the point of this response header?
> + * what if older server? just returns '405 Method not Allowed'.
Those will be translated into SVN_ERR_RA_NOT_IMPLEMENTED.
> +RA->get_commit_editor2()
> +
> + * stash the incoming hash of tokens.
> +
> + * every time we do a CHECKOUT or PUT of a file path, look to see
> + if there's a token available in the hash. If so, put it in the
> + If: header of the request.
> +
> + * send *all* tokens in the If: header of the final MERGE request.
> +
How do you handle keep_locks? Separate UNLOCK requests? Or something extra
for the final MERGE?
Regards,
//Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Dec 13 23:51:17 2004