[Kde-pim] Marketing blocker collection, DEADLINE: 2013-03-10

[Sven Burmeister]

Am Sonntag, 3. März 2013, 19:13:57 schrieb Kevin Krammer:
> > - do not store any kind of configuration in the cache
> 
> Actually there is no config in the cache.

Indeed, let me re-phrase it:

- do not store cache and config in the same DB
- even better: do not store configs in a DB but in a config file

I was sticking to the common notion that akonadi's DB is just a cache. 
Something which you won't change anymore. And something which defines the 
expectations akonadi has to meet in order to gain acceptance.

If users would like configs to be stored in a DB Linux would already have its 
kind of regedit commonly used.

Alternatively to the above notion there is of course a second common notion 
which scares away users: akonadi stores email data in the DB.

If users pick notion 1, they expect the DB to be removable without any side-
effects but the cache gone, like in a browser.

If users pick notion 2, they probably do not like akonadi anyway (it's like 
regedit) and if they do they won't just purge the DB.

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