But beware, funambol can have the nasty side effect of duplicating contacts due to the way it marks which contacts have been sync'ed causing either the phone or computer to reload a fresh set the next time it is connected resulting in 2 sets of the same contacts being present. This is a common problem with other SyncML solutions. Data should be synchronised by date stamp (not contents),
Absolutely not, never. Timestamps are a terrible way to syncronize. Objects should be versioned so changes can be detected easily; most groupware servers [AFAIK, OGo does] support versioning. I believe duplication is not primarily a bug in Funambol but in [possibly various] backends. I haven't seen duplication using the GroupDAV connector. I don't know if the LDAP backend uses it but there is a last-modified operational attribute in most [all?] DSAs. If not used as a timestamp but just as a key it should be a reliable form of change-detected. For LDAP it would seem the DN would be a stable primary key for a contact.
For funambol, this is most likely some sort of client issue which can be difficult to resolve in the server connector, though a bug in the connector code for a particular client could cause the problem, (or a possibly a missmatch between client and server connector). (Funambol uses connectors to handle the translation between a client and the backend database).
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org