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

Re: mod_dav_svn backward compatibility broken?

From: Joe Orton <joe_at_manyfish.co.uk>
Date: 2003-03-04 21:23:50 CET

On Tue, Mar 04, 2003 at 03:16:01PM -0500, mark benedetto king wrote:
> On Tue, Mar 04, 2003 at 01:53:15PM -0800, Ben Collins-Sussman wrote:
> > Branko ÄŒibej <brane@xbc.nu> writes:
> >
> > > Why can't we jiust marshal the uuid as a property that just happens to
> > > be present on every versionable resource? That not only makes sense
> > > semantically (since we should be storing the uuid in the entries file),
> > > it also means that any DAV client will see it, but can ignore it.
> >
> > Um, yes, that's exactly what we're doing. If you use WebDAV to ask a
> > resource for all its properties, you'll see the UUID, DAV props, and
> > user-controlled props.
>
> Right. I think what Brane was getting at is that it should have been
> shipped as one of the user-controlled props (which obviously don't suffer
> from backwards-compatibility issues). I don't see anything wrong with that,
> but I did include it where I did because it is processed in much the same
> way.
>
> Proposed so far to resolve this have been:

Another hack might be to include the UUID as an attribute on a property
which is accepted by 0.18 clients?

I apologise for the ne_xml.h interface, one of its many sins is that it
encourages the application to validate responses, which is pretty
irresponsible.

joe

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Mar 4 21:50:00 2003

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.