19

You can think of Akonadi as a kind of proxy between the application and the data source.

In cases where the source is an actual server, e.g. IMAP server, it comes very close to the proxy concept know for HTTP.

However, there will also be local data sources, such as vCard files, maildir directories, etc.

Cheers,
_

A little bit offtopic, but why it is chosen to use files instead of db? Mysql is a very stable an popular platform. Also it makes creating selects as easy as possible. Also it has never failed me Unless there is something I don't know

Because Akonadi is simply a unified method of access to all PIM resources, allowing many applications to share it. Applications use it to access all PIM data in a single consistent manner, so major changes don't have to be done to all PIM applications to support a new calendar for instance, only Akonadi has to change.

Lukas wrote:A little bit offtopic, but why it is chosen to use files instead of db?

It is of course also possible to use a DB as a resource backend. Files and specialized servers are just other options.

All kinds of storage backends have advantages and disadvantages, so flexibile support allows to use combinations best suited for the actual use case.

Files, for example, have the advantage of being available to non-Akonadi applications as well, but have disadvantages when it comes to locking or change notifications.

Cheers,
_