[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Two DAV problems/questions.

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2005-01-19 01:58:46 CET

Ben Collins-Sussman wrote:
> I'm busy teaching ra_dav to use/send lock tokens when committing.
> First: after building a repository transaction (Delta V "activity"),
> the svn client performs the final commit by sending a MERGE request
> whose source is the activity. This causes all of our checked-out
> working-resources to be "auto-checked-in". But does this have any
> effect on locks attached to these resources? My guess is "no" -- after
> the MERGE, the locks still remain by default. Is that correct?

DeltaV (RFC3253) and WebDAV locks are completely orthogonal concepts.
Thus: "no" (yes, you are correct).

> Second: this final MERGE request needs to send every lock token that
> was attached to every committed file. According to spec, this is
> normally done in the "If:" header. But apache has an 8K length limit
> per request header. Given that our tokens are about 56 bytes long, that
> means a hard limit of about 130 locks. This is a real problem; it's
> easy to conceive of a large commit uploading changes to more than 130
> locked files. What can we do here?
> --> can mod_dav_svn temporarily turn off the limitation on the
> length of the If: header?
> --> if not, can we send the tokens in custom XML in the request
> body? Does the DeltaV spec allow that? Even worse, will that break a
> 1.0 server?

RFC2518bis updates the syntax for the "If" header so that it can be
split across multiple lines. I guess mod_dav shouldbe updated to support
that notation.

> ...

Best regards, Julian

<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Wed Jan 19 02:02:07 2005

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.