On Aug 23, 2006, at 10:05 PM, Jared Rhine wrote:
+ If we *do* want server-side backups for osaf.us, what's
necessary, if
anything, to make Chandler behave as well as possible in the event
server-side data jumps back in time?
If osaf.us reverts to earlier data, Chandler would need some
indication that this has happened. Potentially this could be a
certain resource that Cosmo adds to each DAV collection as a flag
that this collection is out of date. The first Chandler to sync this
collection at this point would be in charge of bringing the
collection up to date. My first thought was to simply have that
Chandler PUT any resource that doesn't match the local ETAG list (and
remove any resources that no longer belong there), but the problem is
that Chandler might not be up to date itself, and thereby overwriting
data that other Chandlers had published just before the Cosmo crash.
I'll have to ponder this some more.
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "chandler-dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/chandler-dev
