[Kde-pim] New Kolab Resource

[Christian Mollekopf]

Hey,

Perhaps you noticed that I yesterday committed the new kolab resource (because 
I broke jenkins ;-)

The new kolab resource is no longer a proxy resource, and provides email and 
groupware data in one. It is essentially a specialized imap resource that 
translates groupware objects directly, so you always have only one copy of the 
data.

This simplifies the code quite a bit, and makes it more efficient for both cpu 
and diskspace. It will also allow to specialize various aspects of the imap 
resource to deliver an overall better experience for kolab users.

Since the kolab resource replaces the imap resource (respectively serves the 
same purpose), you will have to setup your account again if you want to take 
advantage of that. I'm already using it productively, so it's IMO safe, but 
obviously I can't give you any guarantees.

The new kolab resource will eventually replace the kolab proxy resource, 
although I'll keep the proxy around for until frameworks for backwards 
compatibility. You can continue to use the kolabproxy for the time being, and 
it also works in parallel to the new kolab resource.

Note that so far the new kolab resource supports only kolab version 3 and 
newer, if you want to contribute a patch for version 2 feel free to do so, I 
have little incentive to do so ;-)

== Open Problems ==

One open problem is that the resource currently simply ignores groupware 
objects that fail to translate, which makes it impossible to clean those up 
with the resource and breaks the CONDSTORE sync (the affected folder is 
resynced every time).
One possibility would be to insert dummy objects of the relevant type (e.g. 
event), that have the failing message attached and i.e. read "Error: Failed to 
read incidence" (perhaps with an annotation that allows to find them easily).
That would have the advantage that you could clean-up directly from the client 
application (e.g. KOrganizer), the sync would continue to work as usual, and I 
could even offer a little cleanup tool in the resource config that shows you all 
broken items. What do you think?

Also I'm depending on a libkolab version which is either current master or 
head of the 0.5 branch, I'll need to release an according libkolab version and 
properly depend on it.

Cheers,
Christian
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/