KIMAP has a dependency on KIO which is not suitable for android. To remove that we have to stop using KTcpSocket, which means we'll loos the certificate manager, but that is not suitable for android anyways.
Description
Description
| Status | Assigned | Task | ||
|---|---|---|---|---|
| Invalid | None | T1481 Prototype on android. | ||
| Open | None | T1478 Build on windows. | ||
| Resolved | cmollekopf | T2942 KIMAP2 | ||
| Resolved | cmollekopf | T4497 Release KIMAP2 |
Comment Actions
- 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)
- Possibly minor API adjustments (like the insane multi argument callbacks to deliver results).
Comment Actions
KIMAP2 is done for the time being, release is tagged and pending the release announcement for which we have a ticket.