Tickets :: Comment on [#5175] Restructuring the Kolab driver

* Your Email Address
* Spam protection	Enter the letters below: .__ . .. ..___. , [__)\|_/ \| \|[__ \./ \| \| \\|__\|[___ \|
Comment	> We continued discussion on this and it seems the best solution is to > keep the structure as suggested by the current patches. > > > > We will have to define one interface that has to be kept stable > anyhow. Either this will be on the level of the array that is being > transferred between the specific Kolab XML handler (e.g. note.php or > task.php) and the application. Or it is on the level of the XML.php > handler that would be used within each application. > > > > There are two reasons why the first solution might be better: The XML > handling resides fully within the Kolab module. Thus it is also > available to other PHP applications that would use the Horde > Framework modules as a library. In addition the XML.php interface > would be binding for all four applications we are currently > targeting. Specifying the transferred array is something we do per > application. > > > > Since it is important to get the interface right the first time we > commit it, we will still wait with this until the kronolith Kolab > driver has also been converted to the new structure. > >
Attachment
Watch this ticket