W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 2003

RE: MOVEs across file systems

From: Jason Crawford <nn683849@smallcue.com>
Date: Mon, 10 Mar 2003 13:55:29 -0500
To: "Julian Reschke" <julian.reschke@gmx.de>
Cc: "Lisa Dusseault" <lisa@xythos.com>, "'WebDAV'" <w3c-dist-auth@w3.org>
Message-ID: <OF2F2A9B2B.BC9997BA-ON85256CE5.00672B9F@us.ibm.com>




> If you have a system that supports BIND and multiple bindings, but not
> across the full namespace (the common example with multiple filesystem
> backends, where you don't want to add an additional layer on top of the
> basic FS functionality). Let /a and /b represent namespace partitions
that
> reside in different filesystem partitions. An obvious approach would be
just
> to mirror what the filesystem backend allows -- a BIND within /a would
work,
> while a BIND from /a to /b would fail (same for REBIND). However, a
client
> that doesn't expect this error condition would still be able to MOVE the
> resource.
I don't understand this statement.

> In this case, the resource at the target URL of the MOVE request
> would *not* be the "same" resource anymore (it would have a different
> DAV:resource-id).
We might have to accept that for the single binding cases and encourage
them
to do better, but if they don't
support cross-file system bindings and they do a move to another file
system
and the source resource also has additional bindings to it from the
original file
system, then the request MUST be rejected.   If it is not, the server can
not claim
to support the bind spec.

------------------------------------------
Phone: 914-784-7569,   ccjason@us.ibm.com
I do not check nn621779@smallcue.com
Received on Monday, 10 March 2003 14:00:48 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:03 GMT