Next message: Jim Whitehead: "RE: Collection Fetch/Save proposal"
From: jamsden@us.ibm.com
To: ietf-dav-versioning@w3.org
Message-ID: <852568CB.0069349A.00@d54mta04.raleigh.ibm.com>
Date: Fri, 21 Apr 2000 22:53:22 -0400
Subject: Re: Questions on activities
If servers have such an implementation, then they are free to put the
resources anywhere they want, provide any keys they want, etc. The user's
URL is simply a binding to the server-managed resource. There may be no
other bindings, and the server may not even support the BIND method. The
user need never know anything about the server's implementation or where
and/or how it physically stores the resource, what keys it uses to access
it, etc. This is true for any resource type, not just activities.
It is very important the protocol stays implementation neutral to maximize
server implementation flexibility. So I still don't see why activity names
must be managed by the server. But we continue to have similar discussions.
Perhaps I'm missing something.
|--------+---------------------------------->
| | "Geoffrey M. Clemm" |
| | <geoffrey.clemm@rational|
| | .com> |
| | Sent by: |
| | ietf-dav-versioning-requ|
| | est@w3.org |
| | |
| | |
| | 04/21/00 05:59 PM |
| | |
|--------+---------------------------------->
>-----------------------------------------------------------------------|
| |
| To: ietf-dav-versioning@w3.org |
| cc: |
| Subject: Re: Questions on activities |
>-----------------------------------------------------------------------|
From: jamsden@us.ibm.com
I don't think the server should be making up activity (or any
resource) names. These belong to the user creating the activity or
resource. WebDAV collections were introduced to provide a mechanism
for managing namespaces. WebDAV versioning should use this
mechanism and not introduce something else.
Any resource that is commonly implemented as a row in a database (as
is often the case for an "activity") is likely to have a server
defined segment in its name. There will be client defined properties
(such as DAV:display-name), but whenever there are a large number of
objects in a single collection (such as rows in a database), it is
common for the server to assign the key, rather than the client.
Having servers define the names for members in very large collections
is in no way incompatible with the WebDAV namespace mechanism.
Cheers,
Geoff