W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2002

RE: What is left after LOCK/UNLOCK on null resource?

From: Clemm, Geoff <gclemm@rational.com>
Date: Thu, 5 Sep 2002 14:03:24 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B1078391FD@SUS-MA1IT01>
To: w3c-dist-auth@w3.org

Just to avoid any misunderstanding, using the DeltaV protocol
will only allow such interoperation if we get clients and servers
to support the protocol.  Probably I should have said
"would theoretically allow" instead of "would effectively allow" (:-),
but that is one reason I encourage folks to use the DeltaV protocol
in their clients and servers if they want to provide shared long-term
locking functionality.


-----Original Message-----
From: Clemm, Geoff [mailto:gclemm@Rational.Com]

My point about using the DeltaV protocol for "long-lived locking"
(or "shared locking) applications was that using this protocol
would allow a client to effectively interoperate with a wider
variety of servers (both versioning and non-versioning), with the
"version URL" effectively replacing the functionality of the
"shared lock token". 
Received on Thursday, 5 September 2002 14:03:55 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:26 UTC