[Kolab-devel] web groupware

[Gunnar Wrobel]

Hi Thomas,

>> Also I'm not sure if the additional abstraction layer between the "base 
>> driver" and "IMAP storage driver" won't make things avoidable complex. 
>> How would that layer look like?
>
> It would mainly consist of the functionality currently provided by the
> Kolab class within the Kolab.php driver. But it would delegate all
> functionality dealing with storage in IMAP to the specific storage
> driver. It would be somewhat similar to the newer Share driver that
> also has different storage back ends.
>
> I believe one would end up with three to four different storage
> drivers for Kolab:
>
>  - a basic one that enables "old style" handling of groupware objects.
>  - a plain IMAP storage driver
>  - a cached IMAP storage driver
>  - (a cached IMAP storage driver that uses VFS)
>
> The Kolab class would then select the configured back end and delegate
> the calls there.

you were right :) Splitting this up is too complex and can be
avoided. I had to start the splitting in order to see that.

So step 1 (splitting of the Kolab driver) has been completed and
submitted to the Horde team for review.

http://bugs.horde.org/ticket/?id=5097

Cheers,

Gunnar

-- 
____ http://www.pardus.de _________________ http://gunnarwrobel.de _

    >> Mail at ease - Rent a kolab groupware server at p at rdus <<

p at rdus Kolab work is funded in part by KDAB and the Kolab Konsortium