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

[Bug 217] GULP integration

From: <bugzilla@soe.ucsc.edu>
Date: Wed, 8 Feb 2006 11:44:34 -0800
Message-Id: <200602081944.k18JiY2G005832@ietf.cse.ucsc.edu>
To: w3c-dist-auth@w3.org

http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=217





------- Additional Comments From ejw@cs.ucsc.edu  2006-02-08 11:44 -------
Discussed during the Feb. 8 2006 teleconference:

Julian raised an issue with the following paragraph:

 A successful request for a new shared lock MUST result in the
    generation of a unique lock token associated with the requesting
    principal.  Thus if five principals have taken out shared write locks
    on the same resource there will be five locks and five lock tokens,
    one for each principal.

Suggestion was to change this to:

A successful request for a new shared lock MUST result in the
    generation of a *unique lock, with a* unique lock token*,* associated with
the requesting
    principal.  Thus if five principals have taken out shared write locks
    on the same resource there will be five locks and five lock tokens,
    one for each principal.






------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
Received on Wednesday, 8 February 2006 19:44:37 GMT

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