--- Comment #2 from pohly <patrick.ohly(a)intel.com> 2009-07-23 00:45:21 ---
(In reply to comment #1)
(In reply to comment #0)
Yes, if the client update the ORG field and the server update the ORG field the
A later two-way sync, will cause the server send back a contact with *two* org
fields. The underlying eds can store them correctly but :
1) most client can't show a contact with more than one ORG.
2) During sending, synthesis will also only send the contact with one ORG (the
second ORG will overwrite the previous one).
Our sysync_sample_config.xml contains ORG as a simple property (not an array),
so already when we receive the vCard from Google only the later ORG property is
stored in the field list and then encoded again for EDS. This matches the
capability of Evolution, which only supports one ORG.
What does Google do with two ORG properties? Is that visible in the web
I wonder whether it's consistent with vcard for a contact with
more than one
ORG properties. If so, we may need to extend synthesis. If not, we may have to
workaroud for such case: if we receiving a server item with more than one ORG,
we may have to decide which one to store and strip others.
The current behavior is consistent with Evolution, so we shouldn't change the
config. As to handling the duplicate ORG, we already pick the later one. I'm
not sure whether the order is predictable, but it doesn't matter anyway: there
is no good solution for preserving both pieces of information, neither on the
client nor on the server.
I tend to close this issue as "works as intended".
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.