On Tue, 4 Jan 2005 11:44 pm, Armin Bauer wrote: > i will give you an example sync: > > two devices: A and B > > user adds this vcards to device A: > > NAME:blubb > A-ONLY-FIELD:test > > and syncs with B. Now the archive will contain both fields (the > converter has to map the A-ONLY-FIELD of course). the vcard in device B > will look like this (since B discards the A-ONLY-FIELD): > > NAME:blubb > > now the user modifies the contact on device B to: > > NAME:blubb-new > > and syncs again. Now the syncengine sees the information from B but does > a MERGE! with the archive before sending it to A. Therefore A will > receive this vcard: > > NAME:blubb-new > A-ONLY-FIELD:test > > and no information is lost.
Very good, but how does the sync-engine know beforehand that device A supports both NAME and A-ONLY-FIELD, while device B supports NAME field only? The devices must still tell the sync engine at startup which fields they will handle. -- Stewart Heitmann <[EMAIL PROTECTED]> ------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Multisync-devel mailing list Multisync-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/multisync-devel
