On Fri, Jul 06, 2001 at 05:13:29PM -0500, Ben Collins-Sussman wrote:
>
> I'm preparing to jump into ra_dav and mod_dav_svn. In particular, I'd
> like to get properties working over the wire. So I've spent all day
> re-reading the deltaV spec & examples, and Greg's quasi-outdated
> document on how deltaV maps to Subversion:
>
> http://www.webdav.org/deltav
>
> http://subversion.tigris.org/webdav-usage.html
>
> I know that Greg Stein isn't listening to email right now, due to more
> important engagements (:-)), but he may see some of these threads next
> week. Also, it's possible that Joe Orton may know a lot about this.
>
> First, I'd like verification that I understand what mod_dav_svn is
> really doing. It seems like a deltaV server has the job of creating
> lots of "temporary" URLs as way of continually building up state with
> the client. (Since HTTP is a stateless protocol, I guess this is all
> it can do!)
Yeah, exactly.
> mod_dav_svn puts all these temporary URLs into the $svn namespace:
>
> $svn/act/URL/UUID activities (fs transactions in progress)
> PROPFIND, DELETE (abort), MERGE (commit)
>
> $svn/his/[node-id] versioned history resources
>
> $svn/ver/[node-id]/[path] versioned resources -- immutable!
> PROPFIND, GET, REPORT (only read-only ops)
>
> $svn/wrk/[activity]/[path] working resources (being edited)
>
> $svn/blin baseline resources (not done) -- svn revisions?
> $svn/bsel
> $svn/bhis
>
>
> So my first question was originally: where is mod_dav_svn storing all
> this stuff? On disk somewhere?
Yup, mod_dav_svn persists activities using an extra 'activities'
databases (just using APR's dbm interface) in the repostiry, see
mod_dav_svn/activity.c.
joe
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sat Oct 21 14:36:33 2006