[cvs] [Wiki] changed: SyncRoadMap

Karsten Fourmont karsten at horde.org
Fri Oct 21 01:59:46 PDT 2005


karsten  Fri, 21 Oct 2005 01:59:46 -0700

Modified page: http://wiki.horde.org/SyncRoadMap
New Revision:  1.13
Change log:  new items for code cleanup

@@ -21,8 +21,10 @@
 +++ Code Cleanup
 
 This sections lists stuff that does not directly affects functionality but rather the quality of the code
 
+* create meaningful phpdoc source code documentation
+* create a testing backend, test cases for sync sessions
 * 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 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.


More information about the cvs mailing list