W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > July to September 2001

RE: Auto update of VCR when checking an associated working resource

From: Lisa Dusseault <lisa@xythos.com>
Date: Fri, 13 Jul 2001 10:24:26 -0700
To: "Tim Ellison" <Tim_Ellison@uk.ibm.com>, "DeltaV" <ietf-dav-versioning@w3.org>
Message-ID: <HPELJFCBPHIPBEJDHKGKAEBNCJAA.lisa@xythos.com>

> > So are we back to saying that supporting Working Resource
> > feature requires also supporting UPDATE?  That's what I'm
> > trying to avoid.  Is there a better way for these two
> > features to not depend on each other?
>
> No I'm not saying that.  I have an application in mind that creates
> versions and doesn't update any version-controlled resource.  It always
> references the versions by their version URL.  In this case there is no
> need for DAV:auto-update or an UPDATE method, so I would object to making
> them required.

That really badly serves the purposes of non-versioning clients.  The server
can't interact with those clients in your scenario, because those clients
would always just GET the VCR, and end up with the root version instead of
the latest versions.

Let me phrase the problem in these terms, I must find a solution to: How do
I write a server implementation that
 - supports Working Resources
 - supports non-versioning clients

Some of the assumptions I've made in framing this problem are that
 - UPDATE is not supported
 - I may not be able to rely on versioning-aware clients to use the
auto-update flag in CHECKIN.  I don't know how to send an error if they
don't use this flag.
 - It's the wrong thing to always show non-versioning clients the root
version.  They will never have the opportunity to see the latest version.

Lisa
Received on Friday, 13 July 2001 13:24:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 13:57:42 GMT