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

Re: svn list -R of medium-size repository takes 10 hours.

From: Ben Collins-Sussman <sussman_at_collab.net>
Date: 2005-08-22 21:04:07 CEST

On Aug 22, 2005, at 1:54 PM, Jean-Marc Godbout wrote:

> Yes, I was calmly eating my cheerios when I realised that I wasn't
> thinking about backwards compatibility.
>
> 1. If we simply remove all the DeltaV props, then we are preventing
> any old clients from connecting as they expect Checked-in to be there.
>

Actually, I'm not so sure about that. ra_dav usually asks for
specific properties. I don't think it asks for <allprops> very often
at all. You should check the code; it may in fact be perfectly safe
to remove DeltaV props from an <allprop> response.

> 2. If we make the clients query for the has_props, then we would need
> to handle the case of the older server. This is fixable. If we get a
> 404 for that property, then we do an allprop and request everything -
> using the old way to determine has_props. This would be much slower,
> but not break any existing functionality.

That's one solution. But then it means doing two PROPFIND requests
instead of one, when talking to older servers. It reeks of evil:
"Subversion 1.3 now runs 'svn ls' twice as fast, but it's even
*slower* when you point it to a pre-1.3 server!"

There may be more clever solutions. Like, for example, in the
PROPFINDs for vcc, baseline, etc. which lead up to the "final"
PROPFIND, we could add the 'has_props' to our list of props to
fetch. Then we'd know -- early on -- if 'has_props' is supported or
not. Then the final PROPFIND can either be a target list, or an
<allprop>.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Aug 22 21:05:06 2005

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.