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

RE: again: OPTIONS semantics

From: Clemm, Geoff <gclemm@rational.com>
Date: Thu, 26 Sep 2002 18:33:31 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B107839290@SUS-MA1IT01>
To: ietf-dav-versioning@w3.org
Yes, I think it would be fine to consider different backends to be
different servers.  The only thing I'd insist on is that the OPTIONS
request return "update" in the DAV header if the resource identified
by the request-URL supports the UPDATE method.  Beyond that, I'd
just do whatever makes sense for your implementation.


-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@greenbytes.de]

let's take that further -- this is a real implementation issue, not just

I have *one* servlet "/a" that controls access to different backends through
different namespace partitions such as "/a/filesystem", "/a/jdbc" and so
on... One backend may support workspaces, the other won't.

Would you still consider this "multiple" servers?
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 
-----Original Message-----
From: ietf-dav-versioning-request@w3.org
[mailto:ietf-dav-versioning-request@w3.org]On Behalf Of Clemm, Geoff
Sent: Thursday, September 26, 2002 11:22 PM
To: ietf-dav-versioning@w3.org
Subject: RE: again: OPTIONS semantics

I would classify two different servlets as two different 
servers, and so if the servlet handling the OPTIONS request 
does not know about the update feature, then it is expected 
to not return "update" in the DAV header. 
-----Original Message----- 
From: Julian Reschke [mailto:julian.reschke@gmx.de] 
Sent: Thursday, September 26, 2002 5:16 PM 
To: ietf-dav-versioning@w3.org 
Subject: again: OPTIONS semantics 

Just taking an example from section 7: 
"Additional OPTIONS Semantics 
If the server supports the update feature, it MUST include "update" as a 
field in the DAV response header from an OPTIONS request on any resource 
that supports any versioning properties, reports, or methods." 

So assuming my DAV namespace is separated into two parts (for instance by 
servlet) "/a" and "/b". Both parts of the server namespace support 
versioning, but only "/a" supports workspaces. Should the "update" feature 
be reported on "/b" and it's descendants? 
The spec says "yes", but I don't think this is implementable (for instance, 
the servlet responsible for "/b" may not even know about the existence of 
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760 
Received on Thursday, 26 September 2002 18:34:14 UTC

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