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

Re: DeltaV conformance vs backward compatibility in fixing the issue 2151

From: Julian Reschke <julian.reschke_at_gmx.de>
Date: 2006-02-20 13:12:45 CET

Kazutoshi Satoda wrote:
> Hi.
>
> The previous patch for issue 2151(r18513) improves performance only
> in 'svn ls -v' over ra_dav between both patched svn client/server.
> There is another more significant fix for this issue.
> See fix 1 in the following URL.
> http://subversion.tigris.org/issues/show_bug.cgi?id=2151#desc11
>
> The fix is filtering out DeltaV properties from allprop request.
> This is also a way to get conformance with DeltaV. But this breaks
> backward compatibility because old(and existing) ra_dav code is
> expecting that an allprop response contains DAV:version-name and
> DAV:creator-displayname as the last committed revision and author
> respectively. I'm not sure but suspecting ra_serf has same expectation.
> ...

So shouldn't be the first step to fix the svn client code so that
explicitly asks for the properties its interested in? That would allow
full RFC3253 compliance in two versions from now...

Best regards, Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 20 13:16:07 2006

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.