[Tickets #5253] Re: Marking an LDAP source as "read only"

[bugs at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://dev.horde.org/horde/whups/ticket/?id=5253
-----------------------------------------------------------------------
 Ticket             | 5253
 Updated By         | Chuck Hagenbuch <chuck at horde.org>
 Summary            | Marking an LDAP source as "read only"
 Queue              | Turba
 Version            | HEAD
 Type               | Enhancement
 State              | Rejected
 Priority           | 1. Low
 Owners             | 
-----------------------------------------------------------------------


Chuck Hagenbuch <chuck at horde.org> (2007-04-13 07:31) wrote:

> Kolab does not use a database at all. And if somehow possible this 
> should remain that way. With the switch of the Share driver from the 
> Datatree backend to the Kolab IMAP server it is possible to run Horde 
> without a db. On the other hand there are packages like the Perms 
> system that rely on the datatree driver and thus on a db. So far this 
> only resulted in a minor loss of functionality.

There's History also. What are your thoughts on using sqlite for this sort
of thing? Not the best for clustering, but it's a solution that doesn't
require another daemon at least.

> In the long run I certainly want to have either an LDAP based Perms 
> driver or an LDAP based datatree driver. But this currently does not 
> have highest priority.

Please, please don't torture yourself on an LDAP datatree driver -
datatree is being phased out and will be removed entirely with Horde 4.