[dev] [commits] Horde branch master updated. 95427ccd8bcb03db7c9ab306df4aef2844a3a9c4
Gunnar Wrobel
p at rdus.de
Sat Oct 23 20:54:11 UTC 2010
Quoting Michael M Slusarz <slusarz at horde.org>:
> Quoting Michael M Slusarz <slusarz at horde.org>:
>
>> commit e73d7b53f08bbd075e2ab70c19de809a24fad42d
>> Author: Michael M Slusarz <slusarz at curecanti.org>
>> Date: Fri Oct 15 16:02:55 2010 -0600
>>
>> Abstract prefs storage code into Horde_Prefs_Storage.
>>
>> Jan and I talked about using a stack system for retrieving prefs data
>> from storage. After discussion, determined that cache storage won't
>> work in the stack system for several reasons. However, it may be
>> possible to implement otherwise. For example, in Horde, there would be
>> 2 stack drivers. The first is a read-only driver that returns the
>> default values from the prefs.php files. The second would be the
>> persistent storage driver.
>
> To make clear - I haven't implemented this stack. Presently, it is
> only possible to use a single storage driver. Setting defaults and
> running Horde hooks is accomplished by pre/post load stubs that are
> implemented by Horde_Core_Prefs.
>
> Also, any reason to keep the Kolab driver?
Feel free to drop that one.
> It looks like KolabImap is the only driver being actively maintained.
Probably also needs some love. Will look at this once I get Horde4
running on the Kolab server.
Cheers,
Gunnar
>
> michael
>
> --
> ___________________________________
> Michael Slusarz [slusarz at horde.org]
>
>
>
> --
> Horde developers mailing list - Join the hunt: http://horde.org/bounties/
> Frequently Asked Questions: http://horde.org/faq/
> To unsubscribe, mail: dev-unsubscribe at lists.horde.org
>
More information about the dev
mailing list