On Thu, Feb 17, 2011 at 15:27, Ivan Zhakov <ivan_at_visualsvn.com> wrote:
> On Tue, Feb 15, 2011 at 12:44, Hyrum K Wright <hyrum_at_hyrumwright.org> wrote:
>> How far can we go with this? If we're not using cached DAV properties
>> with ra_serf, and ra_serf is the default in 1.7, does it make sense to
>> remove support for them from the 1.7 working copy? It shouldn't be
>> too difficult, and would tighten libsvn_wc up a bit.
> You're talking about different thing: 'wcprops', DAV properties stored
> in working copy. Actually ra_serf with HTTPv2 doesn't use them at all.
> Even usage with server without HTTPv2 support is very limited. Also
> I'm going to implement baseline information caching to ra_serf which
> eliminate several PROPFINDs and make the situation better when server
> doesn't support HTTPv2.
> So my personal opinion that it's good idea to completely remove
> 'wcprops' support from libsvn_wc in 1.7 assuming that will simplify
> the code and improve WCNG performance. As Greg said: "upgrade your
For 1.7, I would recommend leaving "dav props" (aka wcprops) in the
working copy library. At a minimum, for backwards compatibility
purposes. But I think we just don't want to get into ripping that out
right *now*. Let's ship 1.7 first.
I would certainly not be opposed to considering the removal of dav
props from wc in the 1.8 timeframe. I suspect that since we always
intended them to be a *cache*, then we can probably remove their
storage without a problem.
Received on 2011-02-18 12:03:36 CET