[Kde-pim] KIMAP2

[Christian Mollekopf]

Heya,

With KIMAP headed for frameworks as a stable imap protocol implementation, I'm 
planning to start development on KIMAP2.

Plans for KIMAP2 include:
* Removal of the session thread. We currently have a thread per connection 
that handles reading/writing the socket and parsing the responses.
This design seems unecessary complex, and we have crashes in that code until 
today (I have wasted weeks trying to fix it already).
I think the design stems from times where KIMAP was directly used in the UI-
Thread, which is not something we do nowadays anyways, so I think it should be 
unproblematic to get rid of the threading code.
* Support for QRESYNC. An extension for quick resynchronization.
* Get rid of KTcpSocket, which currently adds a dependency to KIO. QSslSocket 
should be good enough, although we'll loose the certificate manager, but that 
won't work on platforms like android anyways.
* Possibly minor API adjustments (like the insane multi argument callbacks to 
deliver results).

I thought about a KAsync::Job based API, but I think it is too early for that, 
so it will stick to the KJob based API we have right now.
(Eventually we'll definitely want to switch though, see [0])

Please note KIMAP2 will not become a framework until it's stabilized, and will 
be versioned according to semantic versioning.

If you have other plans or wishes for KIMAP2 yourself, please let me know.

Cheers,
Christian

[0]https://phabricator.kde.org/diffusion/AKONADINEXT/browse/develop/examples/imapresource/imapserverproxy.h
[1]https://phabricator.kde.org/diffusion/AKONADINEXT/browse/develop/examples/imapresource/imapserverproxy.cpp;456b850448bc306e9e1608fd1707ab9ceeb08c1e$318

_______________________________________________
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/