[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 23:08:04 CET

Justin Erenkrantz wrote:
> On 2/20/06, Julian Reschke <julian.reschke@gmx.de> wrote:
>> How would fixing the client (so that it explicitly fetches the live
>> properties as required by RFC3253) be an incompatible change?
>
> Having the server not return the full list of live properties would be
> incompatible. Updating the client wouldn't be incompatible. But,
> fetching just those two liveprops we need on every request would be
> ridiculously inefficient and very likely not worth it. (We'd have to
> do two PROPFINDs in order to get a single file because allprop doesn't
> do what 2513 says any more. Ugh.)

2518?

In which case I'd recommend to use the extensions in RFC2518bis -- both
in server and client -- that allow you to fetch both in one request. See
 
<http://greenbytes.de/tech/webdav/draft-ietf-webdav-rfc2518bis-14.html#rfc.section.9.1.p.3>.

> However, this isn't a bug in SVN - mod_dav intentionally gives out all
> liveprops on allprops. So, httpd would need to be fixed not
> Subversion - as there's nothing Subversion can do. -- justin

Well, if httpd isn't compliant to the spec it's supposed to implement,
let's fix that. Am I missing something?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Feb 20 23:09:13 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.