On Aug 31, 2006, at 1:54 PM, Jared Rhine wrote:
Open options seem to be:
A) Not worry about this issue until after Beta
B) Add Last-Modified to the ETag Chandler currently uses to
determine if
a resource has changed and should be overwritten
C) Have Cosmo track a version number in addition to the ETag
D) Have Chandler include a version number in the resource and only
overwrite resources if the server-side version number is greater than
the local
For my part, right now I give a +1 to "D", a Chandler-maintained
version
number.
+1 to "D" as well. The time frame for Chandler's implementation of
this would likely be in α5 which is when Chandler's sharing format
will change.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
