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

Re: Puzzle: DELETE of a locked collection

From: Greg Stein <gstein@lyra.org>
Date: Thu, 13 Apr 2000 16:05:00 -0700 (PDT)
To: w3c-dist-auth@w3.org
Message-ID: <Pine.LNX.4.10.10004131602270.13301-100000@nebula.lyra.org>
I believe that I have an answer to this. The trick is to realize that a
no-tag-list can specify a set of OR'd states. So the answer is:

If: (<A>) (<B>) (Not <A>) (Not <B>)

Ugly, but it basically means that every resource will match something, and
that the lock token is provided to navigate through the lock.

Eek.

-g


On Thu, 13 Apr 2000, Greg Stein wrote:
> Consider the following directory structure:
> 
>   Collection         [locked with token A, depth=0]
>    \
>     SubCollection    [locked with token B, depth=infinity]
>      \
>       File1
>       File2          [these inherit token B]
>       ...
>       FileN
> 
> 
> Now, how do you delete SubCollection?
> 
> Note that you must provide token A to remove SubCollection from
> Collection. Also, you must provide token B for SubCollection *and*
> File1..N.
> 
> What's the IF: header look like?
> 
> (presume that you cannot delineate all the (recursive) members of
>  SubCollection and insert them *all* into the IF: header)
> 
> I can't see a way to do it. Normally, no-tag-lists are used for specifying
> locks for a hierarchy. But you must use a tagged-list to specify token A.
> 
> Ideas?
> 
> Cheers,
> -g
> 
> -- 
> Greg Stein, http://www.lyra.org/
> 
> 
> 

-- 
Greg Stein, http://www.lyra.org/
Received on Thursday, 13 April 2000 18:58:58 GMT

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