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

Re: dav props

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2001-07-16 18:53:04 CEST

Joe Orton <jorton@btconnect.com> writes:

> > * I attempted to checkout again over DAV, and got no properties at all.
>
> The patch I posted gets this working.

Whoops, let me go find that post and try it out...

> > $ svn pl A/D/gamma
> > METADATA :
> > 1:foo :
>
> If we make several assumptions:
>
> 1) mod_dav_svn relies on the internal structures that mod_dav uses for
> storing properties, see modules/dav/main/props.c in the Apache 2.0 tree

Hmmmm. I see that DAV props are using a whole fancy `namespace' table.

> 2) we only allow setting user properties through a specific namespace
> e.g. "SVN:custom"

Um, if you're talking about forcing either the user or the client
libraries to auto-prepend this prefix, that's not acceptable. (It
would be an example of one particular RA implementation allowing its
internal details to creep into unrelated libraries.) In this same
vein, we want user props in the repository to look exactly as they do
in the working copy.

  (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.

> Greg may prefer to do this properly, which would require some large
> changes to mod_dav itself AFAICT.

I'm probably getting really confused on this issue, but here are our
immediate needs:

  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.)

So yes, I guess this means making some large changes to both ra_dav
and mod_dav_svn.

   (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?

---------------------------------------------------------------------
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

This is an archived mail posted to the Subversion Dev mailing list.