RE: v6: 12.9 lockdiscovery

Actually he could ask for this information by asking for the lockdiscovery
property with a depth=infinity. Although this is clearly not terribly
efficient. I would refer you to the DASL working group which is creating a
more powerful searching system such that a user could send a request to a
server asking "Return me all the resources which have a lockdiscovery
property which contains a lock I own."

		Yaron

> -----Original Message-----
> From:	Roland Grassmann [SMTP:grassmann@itwm-trier.fhg.de]
> Sent:	Thursday, February 05, 1998 1:21 AM
> To:	Yaron Goland
> Cc:	'howard.s.modell@boeing.com'; w3c-dist-auth@w3.org
> Subject:	RE: v6: 12.9 lockdiscovery
> 
> Yaron Goland writes:
>  > The provisions is that lock discovery returns all outstanding locks,
> who
>  > owns them, and what the lock tokens are. Thus a program that finds it
> is
>  > denied access because of a lock can perform discovery and find out that
> it
>  > is the one with the lock.
>  > 
> 
> Hi,
> 
> maybe this is a slightly different issue, but shouldn't users also be
> able to request a listing of all locks owned by them, not only all
> locks pretaining to a specific resource.
> 
> If, for example user A has locked resources X and Y and forgot all
> about having locked X, shouldn't he be able to ask for a list of all
> ressources he locked. This would enable him to release X (or carry on
> working on it)?
> 
> As far as I understand the current mechanism it only allows A to ask
> for a list of all users having locked Y. If he doesn't know -- or
> remember -- that checking for locks on X would be a good idea for him,
> he won't be able to find out, would he?
> 
> Greetings from Germany
> 
> roland
> 
> 
> -- 
> Roland Grassmann				Institut fuer Telematik
> 						Bahnhofstrasse 30-32
> grassmann@ti.fhg.de				54292 Trier, Germany

Received on Thursday, 5 February 1998 05:56:02 UTC