KMail dependence on Akonadi

[Kevin Krammer]

On Monday, 2017-07-10, 03:26:08, Aleksey Midenkov wrote:
> On Sun, Jul 9, 2017 at 6:44 PM, Kevin Krammer <krammer at kde.org> wrote:
> > On Saturday, 2017-07-08, 11:58:02, Aleksey Midenkov wrote:
> >> On Sat, Jul 8, 2017 at 11:34 AM, Kevin Krammer <krammer at kde.org> wrote:
> >> > On Saturday, 2017-07-08, 02:37:22, Aleksey Midenkov wrote:
> ...
> 
> >> Why you invented some
> >> service if there are commonly used SQL servers?
> > 
> > Not sure what you mean, the Akonadi services is using standard databases
> > for its data management needs: MySQL, PostgreSQL, SQLite are options as
> > far as I remember.
> 
> Then why there is additional proxy process (Akonadi) between KMail and
> DBMS? What special functions this Akonadi service does that require it
> to be additional process? Why can't it be just shared library that
> will adapt this PIM API (so called Akonadi) to DBMS services? In other
> words: put Akonadi as shared library inside KMail, Calendar, etc.
> instead of separate process.

A database server is essentially useless without data and none of them can 
access stored data other than their own.

Extending an existing database server to be able to connect to an IMAP server, 
read a local maildir, connect to a CalDav server or read a local ical file 
would essentially require forking that server's code base and maintaining it 
from there on.

Cheers,
Kevin

-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde/attachments/20170711/0c41a9a5/attachment.sig>