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

Re: Can we remove DAV-props/WC-props from the code now?

From: C. Michael Pilato <cmpilato_at_collab.net>
Date: Wed, 30 Jan 2013 13:20:25 -0500

On 01/30/2013 11:46 AM, Julian Foad wrote:
> It would be awesome if we can now completely remove the code supporting
> 'DAV props' aka 'WC props' in the client side, if it is no longer needed
> there.
> I know little about it myself, but on IRC, Bert said [1]:
> "I would hope we can ignore WC/DAV props. And if somebody suggests it I
> would be +1 on removing them now completely from our client. (The skelta
> update in serf for old style servers makes them unnecessary).
> I think the reason to keep them was serf without http v2, but that should
> be fixed. Using a subversion 1.0 server (pre skelta) would get slower,
> but I don't think anybody cares about that.
> It still works ok.
> The repository diff already makes sure dav props won't show up during
> merge. (I think since 1.7)
> Dav props should nowdays only be written by the update editor, and read
> by some callback api that is initialized with ra sessions. "

libsvn_ra_serf today only interacts with a single DAV prop:
SVN_RA_SERF__WC_CHECKED_IN_URL. That property is...

        - during all switch operations.
        - during non-HTTP-v2, skelta-mode updates.
        - during non-HTTP-v2 commits.
        - during non-HTTP-v2 commits.

C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Enterprise Cloud Development
Received on 2013-01-30 19:21:02 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.