[cvs] [Wiki] changed: SyncRoadMap

[Karsten Fourmont]

karsten  Sun, 09 Oct 2005 03:15:58 -0700

Modified page: http://wiki.horde.org/SyncRoadMap
New Revision:  1.8
Change log:  update to reflect current status

@@ -5,28 +5,26 @@
 ++ Things that need to be worked on
 
 +++ Bugs/Limitations
 
-* The client cannot split data in multiple messages or deal with such splits from the client
-* Synthesis support has to be completed for tasks/calendar/address book
 * History retrival has to be fixed to narrow results to meaningful entries
+* sometimes the synthesis clients crashes upon receiving calendar data.
 * The various vcard/vcalendar import/export functions really need some work. Recurring events are not dealt with at all yet.
-* Initial SlowSync of Evens does millions of datatree reads and still takes way too much time. Somethings wrong with that.
 * when server has a matching anhor it will always do a delta sync, even when the client requests a slowsync
 
 +++ Possible Extensions
 
 * Allow customizations which calendars/addressbooks should be synced. Maybe allow merging of more than one data source (think of private and shared calendar)
 * Proper conflict resolution. current policy is: client wins. (As the client send it changes first.)
-* Aligning Client and Server categories
+* Aligning Client and Server categories (work started on that. Currently visible only for P800/P900)
 * Fancy features like 'delete old entries from client calendar/todo list' etc. to save space on client.
 
 +++ Code Cleanup
 
 This sections lists stuff that does not directly affects functionality but rather the quality of the code
 
 * better error handling (!SyncML): currently no real error handling is in place.
-* finish refactoring: all horde specific stuff should go into backend.php. The rest of the package should be Horde independant
+* finish refactoring: all horde specific stuff should go into backend.php. The rest of the package should be Horde independent
 * event handling is a big mess: the current major design flaw is that the classes in ``SyncML``/command are use for parsing the //input// from the client as well as creating the //output// for the client: this results in a ulgy double-usage of the output method: the output method of Status.php illustrates these two functions: first it's automatically called by the event handler in //SyncML.php// to produce the output in response to a Status element sent from the client. This means producing no output is all. And then it's use to create Status responses as result to other operations (Add, Sync etc.). Here the output method of status is called as well, but this time it should do something very much different: produce an actual "Status" output.
 * each syncml command has a (per message) unique //commandID//. The various output methods take at least the //currentCommandID// and the ContentHandler as parameters. They return the increased //currentCommandID//. Non of these three is necessary: they should be moved to global variables or (better) a global object dealing with the state of one message (one script run) in contrast to state.php dealing with the state between different messages.
 * Check where's the best place to draw the border between the rpc and syncml package. Currently syncml.php in RPC does some XML parsing (for body and header). This should be moved to Syncml to leave RPC will all the //transfer protocol// stuff and Syncml with all the contents.
 * currently the horde api only supports listBy($action,$ts) to retrieve $actions since timestamp $ts. The !SyncML protocol requires that the ending timestamp of the sync timeframe to be exchanged _before_ the actual syncing starts. So we need an additional parameter: listby($action,$ts,$ts_end)