- From: Elias Sinderson <elias@cse.ucsc.edu>
- Date: Thu, 27 Oct 2005 10:47:45 -0700
- To: w3c-dist-auth@w3.org
bugzilla@soe.ucsc.edu wrote: >http://ietf.cse.ucsc.edu:8080/bugzilla/show_bug.cgi?id=14 > Definately a major issue... :-) Summary notes from todays conference call: There are currently servers which both DO and DO NOT change ETags on property changes, hence there is a risk in obsoleting existing implementations regardless of the path the WG takes on this issue. Further, there are clear disadvantages to distributed authoring clients if an ETag changes due to a property update, without the resource body changing. Jim suggests introducing PTag for property changes, and I agree this would be useful, however introducing this into a revision of an existing spec will create problems. Julian suggests that this would belong in a seperate specification. Rough concensus reached to use SHOULD NOT with respect to changing ETags on property changes - Lisa to make edit... Hope this captured the gist of the conversation, please feel free to add anything that may be useful. Best, Elias
Received on Thursday, 27 October 2005 17:47:56 UTC