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

RE: Questions/clarification on MKACTIVITY method

From: Steve K Speicher <sspeiche@us.ibm.com>
Date: Mon, 12 Mar 2001 12:01:00 -0500
To: ietf-dav-versioning@w3.org
Message-ID: <OFF383A9F6.83277138-ON05256A0D.00588A5A@raleigh.ibm.com>

>The purpose of the "new activity" option for CHECKOUT is to allow
>a lightweight client to easily interoperate with a server that
>requires activities.  A client with full activity support (i.e.
>one that utilizes MKACTIVITY) can use a DAV:activity-set-collection
>OPTIONS request to determine where it can allocate activities.

How is a client with full activity support intended to know what a valid
activity name is without much trial-and-error?  I was hoping for something

This way the client can programmatically maintain the activity information
and the end-user could perform simple routines like: "new activity" and
"done with activity" without concern about coming up with a valid activity

>A request has to go to a particular resource, which is then
>responsible for handling the request.  What would be the request-URL
>of the MKACTIVITY method in this case?

Since the client is already aware of the DAV/activity-enabled part of a
URL, couldn't it be used without the additional activity location since the
activity location is not handled by a separate handler, right?

So if the URL http://repo.webdav.org/test-23 and "/" is
DAV/activity-enabled, then could the request be something like this?

   MKACTIVITY /test-23 HTTP/1.1
   Host: repo.webdav.org
   Content-Type: text/xml; charset="utf-8"
   Content-Length: long

   <?xml version="1.0" encoding="utf-8" ?>
   <D:mkactivity xmlns:D="DAV:">

Is the additional XML really needed if the server would "assume" that the
client meant for the server to specify the correct collection?


P.S. Your responses to my newbie questions are greatly appreciated.
Received on Monday, 12 March 2001 12:00:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 20:55:46 UTC