- From: WJCarpenter <bill@carpenter.ORG>
- Date: Thu, 3 Feb 2000 10:21:04 -0800
- To: w3c-dist-auth@w3.org
jamsden> We have to be careful about overloading methods to support jamsden> client use cases. This will cause the protocol to bloat and jamsden> become complex. It will also reduce interoperability and jamsden> create situations where one client's use cases conflict with jamsden> another. Some methods do return failure information that your jamsden> client can use. You also have to allow for the possibility that it's more expensive for a server to answer questions about the details of a LOCK than it is to merely answer yes-or-no about a resource being LOCKed. (E.g., a fixed field in some property table points to a LOCK record stored elsewhere.) -- bill@carpenter.ORG (WJCarpenter) PGP bill@bubblegum.net 0x91865119 38 95 1B 69 C9 C6 3D 25 73 46 32 04 69 D6 ED F3
Received on Thursday, 3 February 2000 13:25:59 UTC