Disconnected IMAP

[Andreas Gungl]

On Wednesday 14 April 2004 08:42, Ivaylo Toshev wrote:
> Shortly: I dont want to have local copies of all IMAP objects.
>
> On Tuesday 13 April 2004 17:29, Bernhard Reiter wrote:
> > Can you elaborate why disconnected imap is a show stopper for you?
> >

The current account based dIMAP / IMAP separation is based on the history of 
the development of KMail and the Kroupware client AFAIK. IIRC there are 
plans to join the dIMAP and IMAP implementation in KMail. It might be 
usefull to decide on a per folder basis for connected / disconnected IMAP.
AFAIK. 
The benefit might be that you could define some folders as dIMAP on 
notebooks to limit the amount of local copies to the messages you really 
need.

While you would like to use online IMAP on an office machine it makes sense 
to use dIMAP at least for notebooks or machines with limited connectivity. 
How else would you access you calendar when you're travelling? Well, there 
are PDAs, mobile phones and other solutions to circumvent the problem. But 
dIMAP is a simple and robust solution (and cheap too).

I'm glad that Kolab supports dIMAP. The other way round (IMAP first an dIMAP 
somewhen later) would disqualify Kolab for offline scenarios. Those 
scenarios are most important when you compare groupware solutions. For only 
you might use eGroupware, phpGroupware etc. as well.

BTW, why do you want to introduce a (SQL) database into Kolab? Kolab is 
interesting because it decided to NOT use a database. Why should I 
administrate a database additionally if it is not really needed for a 
groupware solution? Kolab minimizes the effort to get a groupware server 
running. This is again an advantage in comparision to competing solutions.

Regards,
Andreas