Tickets :: Comment on [#4263] A splitted share driver

* Your Email Address
* Spam protection	Enter the letters below: ______ _ ____ ______ __ \| ____\| \| / __ \ / __ \ \ / / \| \|__ \| \| \| \| \| \| \| \| \ V / \| __\| \| \| \| \| \| \| \| \| \|> < \| \|____\| \|____ \|__\| \| \|__\| / . \ \|______\|______\____/ \____/_/ \_\
Comment	> Ahem, no, that wouldn't scale well :) > > > > On the other hand having a specific kolab share driver is not so much > about supporting horde apps like ansel. It is mainly centered towards > turba, mnemo,nag and kronolith. > > > > The reason for suggesting a specific kolab driver is the fact that > kolab is based on this IMAP-centric model and IMAP is the storage > backend used for all kolab groupware information. > > > > So the original Kolab driver tries to bridge between the IMAP > information and the datatree storage and constantly syncs from one to > the other. And this actually never really worked. > > > > So having this specific share driver helps with kolab, but it will > not be the most efficient choice for having large image galleries in > an e-mail based storage system.
Attachment
Watch this ticket