On Tue, Jan 19, 2010 at 8:33 AM, Kamesh Jayachandran <kam...@collab.net> wrote: >> How does this work without also changing mod_dav_svn? I thought it >> did not already have code to handle this? >> > > <snip from http://www.ietf.org/rfc/rfc3253.txt> > > (DAV:create-working-resource-from-checked-in-version): If the > request-URL identified a version-controlled resource, and > DAV:apply-to-version is specified in the request body, the > CHECKOUT is applied to the DAV:checked-in version of the version- > controlled resource, and not the version-controlled resource > itself. > </snip> > > I think mod_dav does this for us.
That is what I was wondering. >> It sounds great if this fixes the problem. I am still a little >> perplexed as to how this works and how it changes the commit process >> and the interactions with a proxy. >> > > It just does not do the problematic PROPFIND leaving way to CHECKOUT to > figure it out. Any idea how it works? CHECKOUT is serviced by the proxy server right? I would think it would lead to the same problem? Maybe the code winds up creating some kind of floating HEAD link as opposed to tying it to what it determines to be the HEAD revision. -- Thanks Mark Phippard http://markphip.blogspot.com/
