https://bugs.kde.org/show_bug.cgi?id=362938
Daniel Vrátil <dvra...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |dvra...@kde.org
--- Comment #2 from Daniel Vrátil <dvra...@kde.org> ---
Hi,
o2 (https://github.com/pipacs/o2) looks good as well, supports OAuth1 and seems
to be still maintained.
From my own experience with writing Akonadi resources, you should consider
using KIO's KJob instead of directly using QNetworkAccessManager: KIO gives you
integration with KDE proxy settings, certificate chain and other goodies, and
the design pattern of KJobs is well-suited for the ResourceBase API, as it
enforces statelessness (is that a word?), which is a good way to prevent
unexpected and hard-to-debug issues in the resources.
Feel free to talk to us on kde-pim mailinglist or #kontact IRC channel if you
need any help or have some questions regarding Akonadi (our tutorials and
manuals are slightly outdated, so you might get in trouble even if you follow
them...)
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
Kdepim-bugs mailing list
Kdepim-bugs@kde.org
https://mail.kde.org/mailman/listinfo/kdepim-bugs
