W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 1999

Re: Clarification on MKCOL needed

From: Greg Stein <gstein@lyra.org>
Date: Fri, 10 Sep 1999 15:57:52 -0700
Message-ID: <37D98CF0.3CC4AD1E@lyra.org>
To: Brian Stiles <bstiles@starbase.com>
CC: w3c-dist-auth@w3.org
Brian Stiles wrote:
> 
> How can a WebDAV server support MKCOL if the repository the server is
> built upon assigns names to newly created collections (as opposed to
> allowing clients to specify the name)?  Put another way, how can a

It can't. MKCOL is defined as creating the collection specified by the
Request-URI. If your server doesn't do that, it it isn't MKCOL :-)

Is it possible for you to create (internally) the server-specified
collection and then somehow link/alias the Request-URI to point to the
new collection?

If you have a custom client, then you can define a method such as
"STARBASE-MKCOL" which is modelled after MKCOL, but returns a Location
header with the true URI. Another alternative is to return the
"next-collection-name" as a property of the parent collection; this has
transactional problems, though (e.g. what happens if two clients request
the property and then use it in MKCOL?)

Cheers,
-g

--
Greg Stein, http://www.lyra.org/
Received on Friday, 10 September 1999 19:06:39 GMT

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