[Korganizer-devel] [Bug 133614] add caldav support for sharing calendars

[Kevin Krammer]

https://bugs.kde.org/show_bug.cgi?id=133614





--- Comment #75 from Kevin Krammer <kevin krammer gmx at>  2011-01-26 10:23:26 ---
(In reply to comment #74)
> > The cache has two use cases:
> > - having often used data accessible locally
> > - providing offline capability.
> 
> I agree with this requirement.  However, it is a good engineering practice to
> have a well-defined flushing policy for any cache.

Agreed. Akonadi's cache flush policy is based on a timeout in minute
granularity.

> For example, if there is a
> time window that will be cached, then objects outside that window should be
> discarded.

Right, a good policy for data that has some meaningful timestamp attached, e.g.
mails, calendar entries. Doesn't make much sense for contacts though.
Easy for Email but tricky for calendar (due to requiring interpertation of
recurrency rules).

> What I am uncomfortable with is the fact that the user has no
> control over the ever-growing cache files in the home directory.  A good
> example is the modern web browser cache which provides the user with sufficient
> amount of control over what is saved.

Good point. While clearing a resource's cache is already available
programatically, this should be accessible in the UI as well.

> > It is important to note that a common misconception about Akonadi's use of
> > MySQL is that Akonadi requires a per-user instance of mysqld running.
> > 
> > While it is the default option for several reasons, there are quite a number of
> > other ones, including running a central mysqld instance or on the application
> > server or using file based SQLite, ...
> 
> As I have posted in the past (i.e. KAddressBook 4.4), I feel that there has
> been a lack of user experience analysis on the part of the KDE PIM project. 
> Please take a step back and consider the statement above.  Akonadi requires the
> user to start an industrial-strength SQL database server just to store email,
> contacts, and calendar.

See, that's why I used "common misconception". It is so common that it can even
appear in the very context of a clarification that it isn't true.

But that is probably my fault, I tend to get clarifications too long. Let me
try a shorter version:

Akonadi does not require the user to start an industrial-strength SQL database
server.

> The best approach is to use a file-based (SQLite, BDB, ASCII) backend
> that can be easily tested to work on the majority of standard VFS mount points
> (local, NFS, AFS, Samba).

Which is why such options are supported by design. Nice, huh?

> Akonadi calendar timing was conducted on KDE 4.6 RC2.  KCalDAV timing was
> conducted on Kontact 4.4.9.

Ah, good.

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.