<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Demystifying Akonadi.</title>
	<atom:link href="http://vizZzion.org/blog/2010/08/demystifying-akonadi/feed/" rel="self" type="application/rss+xml" />
	<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/</link>
	<description>Sebastian Kügler&#039;s web log</description>
	<lastBuildDate>Wed, 09 May 2012 11:21:01 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.2</generator>
	<item>
		<title>By: Stijn Hoop</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1249</link>
		<dc:creator>Stijn Hoop</dc:creator>
		<pubDate>Mon, 06 Sep 2010 11:08:08 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1249</guid>
		<description>That so-called &#039;solution&#039; for NFS homedirectories really is not a solution in our case. Running another database server with it&#039;s own backup/upgrade solutions just to run a desktop environment? And you suggest this, just for data that is only there as a &quot;local cache&quot;?

I have commented multiple times on bugs 182292 and 179006 that we already have a pretty unworkable situation with Akonadi on Fedora 12 / KDE 4.4, but this article makes me afraid of what will happen once we switch to Fedora 14. I hope there&#039;s time for a proper fix, instead of either suggesting edits to hundreds of configuration files, or setting up more servers.

https://bugs.kde.org/show_bug.cgi?id=182292
https://bugs.kde.org/show_bug.cgi?id=179006</description>
		<content:encoded><![CDATA[<p>That so-called &#8216;solution&#8217; for NFS homedirectories really is not a solution in our case. Running another database server with it&#8217;s own backup/upgrade solutions just to run a desktop environment? And you suggest this, just for data that is only there as a &#8220;local cache&#8221;?</p>
<p>I have commented multiple times on bugs 182292 and 179006 that we already have a pretty unworkable situation with Akonadi on Fedora 12 / KDE 4.4, but this article makes me afraid of what will happen once we switch to Fedora 14. I hope there&#8217;s time for a proper fix, instead of either suggesting edits to hundreds of configuration files, or setting up more servers.</p>
<p><a href="https://bugs.kde.org/show_bug.cgi?id=182292" rel="nofollow">https://bugs.kde.org/show_bug.cgi?id=182292</a><br />
<a href="https://bugs.kde.org/show_bug.cgi?id=179006" rel="nofollow">https://bugs.kde.org/show_bug.cgi?id=179006</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: mps</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1215</link>
		<dc:creator>mps</dc:creator>
		<pubDate>Fri, 03 Sep 2010 22:50:09 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1215</guid>
		<description>Hi Sebas,

This is a great article, many thanks. I have one question - what information does akonadi actually cache for emails? Just the mail headers? Only part of the mail headers? The whole email + attachments? I use a local maildir store for my mails, and when I tried kmail 2 this morning, it used up a huge amount of disk space. What is the estimated cache size in this case? (Maildir volume + 100Mb)? or more like (number of emails x Y kb per email + 100Mb)? It might be good to warn users about this as I was rather surprised by the amount of disk space required. 

cheers
M.</description>
		<content:encoded><![CDATA[<p>Hi Sebas,</p>
<p>This is a great article, many thanks. I have one question &#8211; what information does akonadi actually cache for emails? Just the mail headers? Only part of the mail headers? The whole email + attachments? I use a local maildir store for my mails, and when I tried kmail 2 this morning, it used up a huge amount of disk space. What is the estimated cache size in this case? (Maildir volume + 100Mb)? or more like (number of emails x Y kb per email + 100Mb)? It might be good to warn users about this as I was rather surprised by the amount of disk space required. </p>
<p>cheers<br />
M.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ak</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1199</link>
		<dc:creator>Ak</dc:creator>
		<pubDate>Thu, 02 Sep 2010 20:40:03 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1199</guid>
		<description>Thanks for taking the time to reply. Makes sense. Sounds like I can continue backing up my main email (if ever I had to restore to a new machine without the Akonadi data, Akonadi would re-index anyway, so whether I back that bit up or not is probably optional I would think?)</description>
		<content:encoded><![CDATA[<p>Thanks for taking the time to reply. Makes sense. Sounds like I can continue backing up my main email (if ever I had to restore to a new machine without the Akonadi data, Akonadi would re-index anyway, so whether I back that bit up or not is probably optional I would think?)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1193</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Wed, 01 Sep 2010 19:27:13 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1193</guid>
		<description>I don&#039;t know what will happen then. My assumption would be that your cached data would need to be restored from the backing server. To be sure about that, you&#039;ll better ask on the kde-pim-users list.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t know what will happen then. My assumption would be that your cached data would need to be restored from the backing server. To be sure about that, you&#8217;ll better ask on the kde-pim-users list.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1192</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Wed, 01 Sep 2010 19:24:13 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1192</guid>
		<description>True. I might do a &quot;Demystifying Nepomuk&quot; at some point. There are some other things in life right now that take attention, though. And other important KDE stuff, and work-work.</description>
		<content:encoded><![CDATA[<p>True. I might do a &#8220;Demystifying Nepomuk&#8221; at some point. There are some other things in life right now that take attention, though. And other important KDE stuff, and work-work.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1191</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Wed, 01 Sep 2010 19:21:57 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1191</guid>
		<description>I&#039;m not using POP personally, so all I say has to be taken with a grain of salt.

POP is just as well supported as IMAP, indeed I just took IMAP as an example. So yes, you&#039;ll be able to use Kontact/Akonadi with your setup, too. (Caching emails locally is a generic feature of Akonadi, so that&#039;ll work as well.) As to backing up, there&#039;s a tool which allows you to do easy and safe backups of your Akonadi data, so you&#039;re golden there as well. As to diskspace consumption, I don&#039;t expect any surprises there. (Note that if you use MySQL as backing store, the administrative data of the InnoDB storage mechanism in MySQL will take about 100MB on disk, independent of the amount of data you carry.)</description>
		<content:encoded><![CDATA[<p>I&#8217;m not using POP personally, so all I say has to be taken with a grain of salt.</p>
<p>POP is just as well supported as IMAP, indeed I just took IMAP as an example. So yes, you&#8217;ll be able to use Kontact/Akonadi with your setup, too. (Caching emails locally is a generic feature of Akonadi, so that&#8217;ll work as well.) As to backing up, there&#8217;s a tool which allows you to do easy and safe backups of your Akonadi data, so you&#8217;re golden there as well. As to diskspace consumption, I don&#8217;t expect any surprises there. (Note that if you use MySQL as backing store, the administrative data of the InnoDB storage mechanism in MySQL will take about 100MB on disk, independent of the amount of data you carry.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ak</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1190</link>
		<dc:creator>Ak</dc:creator>
		<pubDate>Wed, 01 Sep 2010 17:52:08 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1190</guid>
		<description>Hi,

This is a great post.

One question I have about email though is that a lot of the scenarios above are about IMAP. I use KDE on a laptop and it has all my email on it and it is all local (downloaded via POP and removed from the server).

Is Akonadi built with this scenario in mind too? (It sounds like it is, but safe to ask, I guess!) Also, I currently back up my email by simply backing up my .kde directory. Where would the Akonadi caches etc get stored and would they be quite large potentially?

Thanks!</description>
		<content:encoded><![CDATA[<p>Hi,</p>
<p>This is a great post.</p>
<p>One question I have about email though is that a lot of the scenarios above are about IMAP. I use KDE on a laptop and it has all my email on it and it is all local (downloaded via POP and removed from the server).</p>
<p>Is Akonadi built with this scenario in mind too? (It sounds like it is, but safe to ask, I guess!) Also, I currently back up my email by simply backing up my .kde directory. Where would the Akonadi caches etc get stored and would they be quite large potentially?</p>
<p>Thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: alsuren.wordpress.com/</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1188</link>
		<dc:creator>alsuren.wordpress.com/</dc:creator>
		<pubDate>Wed, 01 Sep 2010 13:12:58 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1188</guid>
		<description>The impression I get is that akonadi is mostly meant to be a unified cache of what&#039;s available from other sources. This suggests a few things to me:

It should probably be stored locally, rather than over yet another network connection (IMAP on server-&gt;terminal-&gt;MySql on server doesn&#039;t sound like it&#039;d be very good for your corporate network).

It should probably be resilient to the db being deleted from under it.

What happens if you just move it into /tmp and delete it when the user logs out? Is akonadi well-designed enough to deal with that efficiently, or would it cause the entire IMAP directory to be pulled down on each new login?</description>
		<content:encoded><![CDATA[<p>The impression I get is that akonadi is mostly meant to be a unified cache of what&#8217;s available from other sources. This suggests a few things to me:</p>
<p>It should probably be stored locally, rather than over yet another network connection (IMAP on server-&gt;terminal-&gt;MySql on server doesn&#8217;t sound like it&#8217;d be very good for your corporate network).</p>
<p>It should probably be resilient to the db being deleted from under it.</p>
<p>What happens if you just move it into /tmp and delete it when the user logs out? Is akonadi well-designed enough to deal with that efficiently, or would it cause the entire IMAP directory to be pulled down on each new login?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jucato</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1185</link>
		<dc:creator>Jucato</dc:creator>
		<pubDate>Wed, 01 Sep 2010 05:12:49 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1185</guid>
		<description>Great post! Take away some of the time/release-related portions and you have the makings of a nice high-level article about Akonadi. IMHO, we need these kinds of bird&#039;s eye-view stuff to communicate better to users and developers the benefits of what our developers have been working on. Give a users why they would want to have Akonadi and attract developers in using the framework.

We also need these kinds of write-ups for NEPOMUK and Strigi (and maybe perhaps Phonon and Solid?). I saw some content on the community/promo wiki, but something a bit more formatted (or to use aaron&#039;s new favorite word, &quot;elegant&quot;) would probably be good. Maybe something like the old plasma.kde.org or phonon.kde.org sites?</description>
		<content:encoded><![CDATA[<p>Great post! Take away some of the time/release-related portions and you have the makings of a nice high-level article about Akonadi. IMHO, we need these kinds of bird&#8217;s eye-view stuff to communicate better to users and developers the benefits of what our developers have been working on. Give a users why they would want to have Akonadi and attract developers in using the framework.</p>
<p>We also need these kinds of write-ups for NEPOMUK and Strigi (and maybe perhaps Phonon and Solid?). I saw some content on the community/promo wiki, but something a bit more formatted (or to use aaron&#8217;s new favorite word, &#8220;elegant&#8221;) would probably be good. Maybe something like the old plasma.kde.org or phonon.kde.org sites?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sebas</title>
		<link>http://vizZzion.org/blog/2010/08/demystifying-akonadi/comment-page-1/#comment-1177</link>
		<dc:creator>sebas</dc:creator>
		<pubDate>Tue, 31 Aug 2010 17:01:20 +0000</pubDate>
		<guid isPermaLink="false">http://vizZzion.org/blog/?p=1586#comment-1177</guid>
		<description>This blog has moved. Not all nameservers might have updated yet. If you see this comment, you&#039;re on the new site  already.</description>
		<content:encoded><![CDATA[<p>This blog has moved. Not all nameservers might have updated yet. If you see this comment, you&#8217;re on the new site  already.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

