[kdepim-users] Online sync of Kontact?

[Ingo Klöcker]

On Monday 08 February 2010, Werner Joss wrote:
> Am Monday 08 February 2010 21:18:58 schrieb Ingo Klöcker:
> > It's not a weird reason. The problem is that KAddressBook and
> > KOrganizer assume that they have fast access to the data. They
> > were not designed to work with remote address books or calendars.
> > (LDAP does work somehow in KAddressBook, but this is only works
> > for LDAP.) This is why using IMAP instead of DIMAP would be
> > insane.
> 
> ok, that sounds reasonable (at least, somehow, although I doubt it
> would be impossible to access address data in tiny vcards over a
> network at acceptable performance)

The problem here is that every application using the address book (and a 
lot of KDE applications do use the address book) will read the whole 
address book (i.e. all the available vcards). And after each change to 
the address book all application will re-read the whole (!!!) address 
book because they have no way to tell what contact changed.

This behavior is already insane when it's done locally (because all of 
those applications did load the whole address book into memory). It's 
not tolerable (by the user) when it's done remote. Note, that Akonadi 
also fixes this problem, i.e. with Akonadi the address book data is kept 
in memory only once. All applications using Akonadi just keep those 
parts of the data in memory which they actually need, e.g. for the auto-
completion of the email addresses entered in KMail.


> > The main reason for requesting this to work over IMAP was that in
> > earlier times one had to get the whole IMAP account via DIMAP. This
> > problem was fixed by the introduction of local subscription of
> > folders. Using this feature you can create a normal IMAP account
> > for your mail and a DIMAP account for the groupware folders. For
> > the normal account you subscribe to the mail folders and for the
> > DIMAP account you subscribe to the groupware folders.
> 
> that was introduced later, and can be considered a workaround, yes.
> at least, it solves the problem of having to keep a complete copy of
> what is on the server just for the sake of being able to use the
> imap-groupware feature.

Exactly. It is a workaround. The real fix comes with Akonadi.


> > With Akonadi we will get rid of the distinction between IMAP and
> > DIMAP. What is cached locally will then be controlled by caching
> > policies which can be defined per folder.
> 
> fine.
> I'm still trying to figure out what can be done with akonadi ATM (4.4
> RC2). didn't find a way to add a 'imap folder based addressbook' so
> far, though. maybe this is just not yet available.

AFAIK the Kolab resource has not yet been ported to Akonadi. Hmm, maybe 
I'm wrong. There is an entry "Kolab Groupware Server" in the "Add 
Address Book" dialog.

If that doesn't work then you have to use "KDE Address Book 
(traditional)" and then "Address Book on IMAP Server via KMail".


Regards,
Ingo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdepim-users/attachments/20100209/37b842c9/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM users mailing list
kdepim-users at kde.org
https://mail.kde.org/mailman/listinfo/kdepim-users