https://bugs.meego.com/show_bug.cgi?id=22783
pohly <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #4 from pohly <[email protected]> 2012-05-09 11:41:27 UTC --- (In reply to comment #3) > Almost done. See 409 mail thread(s) and commits. > > Last open: detect whether storages really support full UID semantic, express > that in the CTCap and adapt the engine's logic accordingly (= remove > hard-coded > "local sync == use UID" hack). Merged into master branches for 1.3: commit 314f0736381fa1300bf52bfc5388e61e06083e30 Author: Patrick Ohly <[email protected]> Date: Thu Apr 26 14:27:22 2012 +0200 local + remote sync: negotiate UID support via SyncCap (BMC #22783) This uses the new libsynthesis support for adding and checking entries in the SyncCap to detect per datastore whether UID/RECURRENCE-ID are truly globally unique and thus can be used to finding pairs. The presence of the property alone is no guarantee for that. Previously this kind of pairing was enabled only for local sync, which was a hack which didn't work for local backends which didn't support UID (for example, Maemo 5 calendar). It also didn't work for mixtures of datastores with and without that kind of support. "1122583000" was randomly chosen as pseudo sync mode. It is a number because strings confuse Funambol. Note that SYNCMODESUPPORTED() only works inside the compare script. -------- Product: SyncEvolution Component: SyncEvolution MeeGo Release: unspecified Severity: normal Priority: High Keywords: Status: RESOLVED Who: [email protected] Assigned To: [email protected] Target Build: --- Flags: Changed: Status Resolution -------- https://bugs.meego.com/show_bug.cgi?id=22783 -- Configure bugmail: https://bugs.meego.com/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
