On Mar 2, 2006, at 11:03 AM, Brian Moseley wrote:
On 3/2/06, Morgen Sagen <[EMAIL PROTECTED]> wrote:
Ok. Although I've always been hoping for ACID transactions and the
ability to send/receive 'sync diffs', if we decide we're going to
yeah.. the biggest issue i have with this approach is that it adds a
lot of complexity to cosmo and chandler specifically for syncing
between each other that goes mostly or completely unused when chandler
talks to a different server or when a different client talks to cosmo.
i'd love to explore the notion of adding transaction support to webdav
so that we could do an entire sync as an atomic operation.
jackrabbit's webdav implementation of jcr remoting maps jcr
transactions to a sequence of webdav requests, so we could look at
that to to get a handle on the issues.
we could also potentially do diff-based sync with webdav someday, but
that would require us to implement versioning in cosmo and would
require logic on top of the webdav layer in both chandler and cosmo.
that might also be a webdav extension in the making ;)
These are all great general extension ideas that would be useful not
only between Chandler and Cosmo but in general. The diff-based synch
is something I've proposed in the past :)
Lisa
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "Dev" mailing list
http://lists.osafoundation.org/mailman/listinfo/dev
