On Thu, Nov 6, 2008 at 7:46 AM, Julian Reschke <julian.reschke_at_gmx.de> wrote:
> Mark Phippard wrote:
>> ...
>> I think getting rid of all the PROPFIND stuff will be the biggest win
>> here.
>> ...
>
> Out of curiosity; do we have a trace or a document that shows what's going
> with respect to PROPFIND?
I don't know that I ever dumped a trace into a document, but it would
do several PROPFIND operations to get where it needed. For example,
one on the public URL to get the VCR, then another to get the VCC,
then another to get the BC. I seem to recall them coming in groups of
four.
> I have that feeling that performance could be improved by simply taking
> advantage of some of the more advanced WebDAV features (such as the
> DAV:expand-property REPORT).
In this case, that would compress 3 or more PROPFIND operations into 1
REPORT. But we're going to return a few key URLs in the initial
OPTIONS response, so we've essentially got the count down to 0.
The short answer to this approach is "WebDAV is fine, so we'll keep
that around; DeltaV has failed, so we're going to ignore it." We're
not going to worry about activities, use of CHECKOUT to create working
resources, using a MERGE to create a new version, etc. The resource
model and operations on it are now more aligned with the svn FS
interface/model.
(and by "failed", I mean there has been zero uptake in the software
world that I'm aware of, and most definitely no interoperability)
Cheers,
-g
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: dev-help_at_subversion.tigris.org
Received on 2008-11-06 19:27:27 CET