If the horde api would provide me with this info directly (maybe just store it in a static var and provide a getLastTS() method in Driver), that would be great and eliminate costly and redundant DataTree calls. My current implementation deals with this as follows: directly after a client induced change is done in horde, state.php's gettsforAction is called to find out the biggest=latest ts for the given guid. Simply storing the guids in the session is not sufficient: the changes are made _after_ the end timestamp (see a)) of the current sync so you'll dupe them in the next sync. You have to somehow "tag" them to avoid echoing (and thus duplicatinging) them back to the client. So when in step 2), the horde api is called with a request like "give me all changes in horde since the last sync", you get the changes induced by the client in step 1) as well. So we need an additional parameter: listby($action,$ts,$ts_end)ġ) the clients sends its changes to the serverĢ) the server sends its changes to the client. The SyncML protocol requires that the ending timestamp of the sync timeframe to be exchanged _before_ the actual syncing starts. Timestamp and Horde API IssuesĪ) currently the horde api only supports listBy($action, $ts) to retrieve $actions since timestamp $ts. You can test the behavior by trying to import/export files with this iCalendar/vCard data into Kronolith/Nag/Turba using their respective import/export menu entries. This is more of a general Horde issue than about SyncML. So we need to test as many of these formats as we can get our hands on. If you have tricky stuff like recurring events, inline photos or other exotic data in the file (or got them "treated" by Outlook), Horde or your phone might quickly get a hickup. SyncML itself doesn't understand these things: it just passes them around between the phone and the external Horde API as-is. Data IssuesĪnother common area of problems are the various implementations of the text/x-vcalendar,vcard.
The parsed result is stored in /tmp/sync/devinf.txt. This gets stored in /tmp/sync/client_01.xml when you start with an empty /tmp/sync/ dir. We are especially interested to see the device information section that the phones sends in its initial packet. Otherwise mail the offending XML and/or log files to the mailing list.Īs many phones/PDAs/whatever as possible should be tested against the code.
Horde remove duplicate messages Patch#
If you can provide a patch to make something broken work: great! The XML files in /tmp/sync/, the Horde log file and the PHP error log should be helpful. SyncMLCreateTestCases: information on SyncML test cases.It is also useful to clear out the Horde log file and /tmp/sync/ to get a better feel for what is from the current sync attempt and what is not. Users can also delete all or individual synchronization session from their Horde preferences. You'll have a lot of entries in the syncml_* database tables that you can empty to try a fresh start. You can clear all session files (assuming the default backend) with rm -f /tmp/sess_*. SyncML/ ConformanceTestSuite shows which test we currently pass or fail. The SyncML Conformance Test Suite can be downloaded from sourceforge: Fancy features like 'delete old entries from client calendar/todo list' etc.(As the client send it changes first.) (I think this has been changed to: create duplicate) This has already been implemented for address books. Allow more customizations which resources calendars/tasklists should be synced.Kronolith can't properly deal with more complex recurring events.
These bugs are not directly in the SyncML module but in the various Horde applications that store the data When doing a SlowSync, the Server could handle a replace request by the client better than just converting it into an add: the server should check if this client sent element exists on the server.However it is supported when the client sends split data. Splitting a long data entry (like a 60k memo) into multiple messages is not supported when sending data to the client.Things that need to be worked on Bugs/Limitations in SyncML
Horde remove duplicate messages simulator#
0 kommentar(er)
