W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > January to March 1998

RE: v6: 12.9 lockdiscovery

From: Yaron Goland <yarong@microsoft.com>
Date: Wed, 4 Feb 1998 17:15:17 -0800
Message-ID: <3FF8121C9B6DD111812100805F31FC0D0113C822@red-msg-59.dns.microsoft.com>
To: "'howard.s.modell@boeing.com'" <howard.s.modell@boeing.com>, w3c-dist-auth@w3.org
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.

		Yaron

> -----Original Message-----
> From:	howard.s.modell@boeing.com [SMTP:howard.s.modell@boeing.com]
> Sent:	Wednesday, February 04, 1998 3:50 PM
> To:	w3c-dist-auth@w3.org
> Subject:	RE: v6: 12.9 lockdiscovery
> 
> okay .. let me pose this simple one (and I apologise in advance
> if I'm repeating something already gone over) ..
> 
> suppose a user gets a "lock token" and subsequently loses/misplaces it
> (and it
> has to be something discrete, so that he/she can "affix it" to 
> different requests/commands ..) ..
> 
> .. can he request the server to "remind" him of it?
> .. can he instruct the server that the lock should be 'forgotten'
>  and all things it is used on are now "free"?  Can he/she do so
> without specifying the specific lock to "forget"?
> 
> Like any kind of identifier or key, unless it is so intimate (like your
> name or a scar or tattoo) .. it can be lost or accidentally deleted.
> 
> What are teh provisions for this?
> 
> <signed>
> Howard S. Modell
> ________________________________________________________________________
>  Adv.Computing Technologist/2         POBox 3707, m/s 4A-25, Boeing D&SG
>  howard.s.modell@boeing.com           Seattle, WA 98124-2207
>  http://warlok.ds.boeing.com/~howie/  (206)662-0189[v] (206)662-4018[f]
Received on Wednesday, 4 February 1998 20:15:44 GMT

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