W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > April to June 2001

Can you BIND lock-null resources?

From: Alan Kent <ajk@mds.rmit.edu.au>
Date: Fri, 22 Jun 2001 10:29:22 +1000
To: WebDAV <w3c-dist-auth@w3.org>
Message-ID: <20010622102922.B14654@io.mds.rmit.edu.au>
Is it expected that you should be able to BIND a lock-null resource?

I am in the process of trying to come up with a software design for
the programmers here to implement WebDAV (first) and then DeltaV (later).
We want to build a fairly generic lump of code to do all the protocol
messing around with a fairly clean and simplified to the underlying
'file system of resources'.

So far I have put the LOCK mechanisms into the WebDAV library layer
(because they are based on URIs). I am also trying to keep the
'lock-null' resource concept in the WebDAV layer since they are
tightly related to locks. My current proposal is to keep track
of lock-null resources with properties that have been set and then
copy those properties over to the real resource when it is created
later (if I have understood things correctly).

I realise BIND is not in the base WebDAV spec, but I want to keep
what is done future proof.

There are two variations of questions I guess I have.

(1) Does the spec prohibit BIND-ing to a lock-null resource?
    (OK, I am being lazy and have not reread the spec again to
    verify this question - but the next question is the real question)

(2) Regardless of the spec, do people think its acceptable to fail
    BIND requests to a lock-null resource with an error? (Is there
    any reason why someone would want to do it before doing a PUT
    or MKCOL etc?)

Alan

ps: Thanks to all for time spent answering these questions.
Received on Thursday, 21 June 2001 20:29:55 GMT

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