Joe Orton <jorton@btconnect.com> writes:
> > 1. All DAV, DeltaV, and mod_dav_svn-specific properties need to be
> > stored in their own apr dbm table in the repository, not in the
> > repository itself.
> >
> > 2. All regular, subversion user properties need to stored in the
> > repository in un-mangled form, and generally need to appear
> > un-mangled on both ends of the network. (If the network layer
> > wants to mangle during transport, that's its own business.)
> >
> > (option A) If ra_dav wants to secretly prepend "SVN:" to all user
> > props, and if mod_dav_svn wants to secretly remove them before
> > storing them in the repository -- then great, that's fine. I guess
> > secret prepending & removal would have to work in the other
> > direction too.
> >
> > (option B) The two ends of the pipe need to distinguish between
> > Subversion properties and DAV properties, since they'll be handled
> > differently. It sounds like this is the "right" way to do things.
> >
> > So what should we do, Joe? Option A or option B?
>
> Both :) The patch I posted does all the client-side stuff necessary, I
> think. But to satisfy goal (1) above is a really big job.
Joe, as a Knight of the Subversive Table, can we send you on this
special quest? Karl, Mike, and I are all really busy working on other
problems.
You're the best man for the job, not just because you've written the
client-side stuff already, but because you're most likely to
understand ra_dav and mod_dav_svn -- you know what Greg is thinking.
What you call a "big job" is *gargantuan* for the rest of us. :-)
---------------------------------------------------------------------
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