[Kolab-devel] horde as kolab's web frontend or not

Jan Schneider jan at horde.org
Tue Jul 4 11:23:58 CEST 2006

Zitat von Gunnar Wrobel <wrobel at gentoo.org>:

>> So the question is whether horde really needs it. This is something
>> that Jan could probably answer. I not yet deep enough into Horde
>> shares to understand the requirements. But I guess there might be ways
>> to omit the standard way horde handles shares. If there would be no
>> need to store additional data on the groupware shares then it would
>> also be possible to get rid of the datatree.
> I did take another look at the relation between Horde Shares and the
> DataTree driver.
> The Share concept is somthing that is used by all horde apps that are
> relevant for the kolab groupware features. So it definitely has to be
> used.

Correct. Horde *can* be configured without a DataTree backend, but  
then you loose all groupware functionality, i.e. you only have one  
personal calendar/tasklist etc.

> Data about Horde Shares is kept within the DataTree. From the code
> segments I have read so far and from the functionality provided by the
> Share concept I am still convinced that the data saved for Horde
> Shares only comprises of information that is provided by the IMAP
> folders themselves. So I would say it is not necessary to duplicate
> that information within the datatree.
> The DataTree concept is not only used for Shares within Horde
> though. There are other parts that use it as well for storing
> arbitrary data values. So it would not be possible to write a DataTree
> driver that is based on imap folders.

Correct too. The DataTree library provides an API to access tree  
structures stored in a flat database backend. It is used for shares,  
permissions, groups (if not provided by ldap or a userland hook), and  
in some applications that use tree structures, like the photo gallery,  
the bookmark application etc.

> I guess the most logical solution would be to extend the Share concept
> and provide different drivers for this package. The current version
> could be split in an abstract Share definition and a datatree
> driver. Then it would be possible to provide a specialized kolab
> driver that uses the IMAP folder information.

Correct three. The Share library doesn't use drivers at all at the  
moment, it's hardcoded to use DataTree. It might be possible to extend  
it to use a Kolab driver, though you still loose the other  
functionalities provided by the DataTree API.

> This solution would also allow to get rid of the DataTree for a
> Kolab-oriented Horde installation.
> Jan, should I rather post this to the horde mailing list?

At some point we should discuss this on the Horde development list, yes.


Do you need professional PHP or Horde consulting?

More information about the devel mailing list