Re: wcprops and wc-ng

It wouldn't be a bad idea for wcng to provide an API for arbitrary programs
to store some key-value pairs in the wc, namespaced (either explicitly by a
third arg or implicitly in the key) by program. gvn really would have wanted
that, say. So you would just use this general storage in the svn:dav1:
namespace or something for the old wcprops.

--dave

On Mar 18, 2009 10:19 PM, "C. Michael Pilato" <cmpilato_at_collab.net> wrote:

Hyrum K. Wright wrote: > Greg, > It appears that the currently failing tests
on trunk over ra_neon a...
Not sure if this helps you to decide or not, but the current WC
implementation has two different property stores, one for regular versioned
properties (which has both BASE and WORKING), one for wcprops (which has ...
neither, really). The wc-props abstraction isn't strictly required going
forward, but when talking to pre-HTTP-v2 servers, the absence of wc-props
has the potential to vastly slow things down.

(There's a third concept called "entry props", but these find their storage
as fields in the svn_wc_entry_t.)

--
C. Michael Pilato <cmpilato_at_collab.net>
CollabNet   <>   www.collab.net   <>   Distributed Development On Demand
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1353462
------------------------------------------------------
http://subversion.tigris.org/ds/viewMessage.do?dsForumId=462&dsMessageId=1355189