W3C home > Mailing lists > Public > ietf-dav-versioning@w3.org > April to June 2002

AW: server defined activity URLs

From: Sohn, Matthias <matthias.sohn@sap.com>
Date: Mon, 8 Apr 2002 12:04:52 +0200
Message-ID: <FAFE609CB754D311B60C0008C75D35560999D5BE@dbwdfx14.wdf.sap-ag.de>
To: "Ietf-Dav-Versioning@W3. Org" <ietf-dav-versioning@w3.org>
Hi,

The <DAV:displayname> of the activity could be set to the URL defined in 
the client request. I.e. for the sample given below <DAV:displayname> of 
the activity would be 
	/act/test-23

But still my question is open if it would be legal that the server moves 
the activity permanently directly on creation ...

regards
Matthias

   -----Ursprüngliche Nachricht-----
   Von: Sohn, Matthias 
   Gesendet: Dienstag, 26. März 2002 10:58
   An: Ietf-Dav-Versioning@W3. Org
   Betreff: server defined activity URLs
   
   
   Hi,
   
   suppose we want to implement a distributed DeltaV server which allows
   propagation 
   between workspaces residing on different servers. In order 
   to ensure unique
   activity names
   (needed to ensure activity URL uniqueness if activities are also
   distributed) in this scenario 
   we would like to have server defined activity URLs.
   
   Would it be DeltaV compliant to achieve that by using the 
   response defined 
   in section "10.3.2 301 Moved Permanently" of the HTTP 1.1 
   spec (rfc2616) ?
   
      >>REQUEST
   
        MKACTIVITY /act/test-23 HTTP/1.1
        Host: repo.webdav.org
        Content-Length: 0
   
   instead of
   
      >>RESPONSE
   
        HTTP/1.1 201 Created
        Cache-Control: no-cache
   
   we would like to use
   
      >>RESPONSE
   
        HTTP/1.1 301 Moved Permanently
        Location: /act/test-23-9C0BC5DA776811D5B3490001021DCD13
        Cache-Control: no-cache
   
        <HTML body containing href to new URL>
   
   regards
   Matthias
   
   
Received on Monday, 8 April 2002 06:05:26 GMT

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