http://bugzilla.moblin.org/show_bug.cgi?id=3479
--- Comment #2 from Chen Congwu <[email protected]> 2009-08-09 22:22:42 --- I have several questions regarding the api implementation. Do we need to impl this concurrent feature for all backends? (groupwise, google, exchange, etc.) When is eds-dbus port ready? Do we need work on this feature on both bonobo and dbus? If so, which one has more priority? [1] http://mail.gnome.org/archives/evolution-hackers/2009-August/msg00004.html (In reply to comment #0) > If a user edits items while a synchronization is running, then all kinds of > "interesting" things can happen: change is overwritten by server change > (definitely!), change is made locally but never sent to server (not so sure), > ... > > Part of the problem is that the EDS API is prone to race conditions. This > needs > to be fixed first, as discussed with the EDS developers: > http://www.mail-archive.com/[email protected]/msg03029.html > > Since that discussion I have implemented automatic restore from backup, which > has > changed my view on the necessary APIs a bit: it would be nice to store > items with a specific REV or LAST-MODIFIED if the libebook/libecal user > knows what he is doing. Not bumping these fields when restoring an items > has the advantage that other clients which were in sync with the > restored data don't see any unnecessary changes. > > The other part of the problem is getting a set of item ID + revision string > (REV for contacts, LAST-MODIFIED for event/tasks) in an atomic way. I'm not > sure whether the current methods are really atomic. But worse, they are also > much slower than they could be because we have to transmit the whole content > of > the database via D-Bus just to extract the much smaller set of required > information. > > Ross wanted to work on a call to return pairs of UID+REV for libebook. I don't > think he got very far with that, though. I think this is a fairly import > optimization. -- Configure bugmail: http://bugzilla.moblin.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching someone on the CC list of the bug. _______________________________________________ Syncevolution-issues mailing list [email protected] http://lists.syncevolution.org/listinfo/syncevolution-issues
