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

Re: svn commit: r1393521 - in /subversion/trunk/subversion: include/svn_props.h tests/cmdline/svnlook_tests.py

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Thu, 4 Oct 2012 11:19:47 -0400

On 10/04/2012 11:01 AM, Ben Reser wrote:
> I recall trying to do that and it wouldn't work. I do believe
> namespaces is how we resolved it for svn:foo style properties. If
> we're going to be doing svn:foo:bar style properties then we can
> probably resolve it for svn:foo properties that way by adding a
> namespace for them. As I recall there was no clean way to tell the
> client what the namespace meant. Specifically how do you get from
> randomnamespacename -> cvs2svn:cvs-rev. The places where we could put
> that information had other character restrictions that made it
> difficult.

You may be right. I've not spelunked in the DAV specs for quite some years
now. I can see that PROPFIND responses carry the sort of information I was
talking about:

<D:response
   xmlns:S="http://subversion.tigris.org/xmlns/svn/"
   xmlns:C="http://subversion.tigris.org/xmlns/custom/"
   xmlns:V="http://subversion.tigris.org/xmlns/dav/"
   xmlns:lp1="DAV:"
   xmlns:lp3="http://subversion.tigris.org/xmlns/dav/"
   xmlns:lp2="http://apache.org/dav/props/">

But I haven't really looked to see if PROPFIND *requests* can do the same,
or what the state of PROPPATCH requests/responses are in this respect.

-- 
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development

Received on 2012-10-04 17:20:32 CEST

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