<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title><![CDATA[Ubuntu brainstorm]]></title>
    <link>http://brainstorm.ubuntu.com</link>
    <description><![CDATA[Post your ideas and vote for the entries you like. Please read the posting <b><a href="https://wiki.ubuntu.com/Brainstorm">guidelines</a></b> and <b><a href="http://brainstorm.ubuntu.com/advanced_search">check</a></b> if your idea has been posted already! ]]></description>
    <language>en-us</language>
    <pubDate>Tue, 02-Dec-2008 00:00:00 UTC</pubDate>
    <lastBuildDate>Tue, 02-Dec-2008 00:00:00 UTC</lastBuildDate>
    <generator>QAPoll module</generator>
 

    <item>
      <title><![CDATA[[28] Unify the mail storage backend]]></title>
      <link>http://brainstorm.ubuntu.com/item/15943/</link>
      <description><![CDATA[All mail clients use a different backend to store emails. But they all share the same basic features.<br /><br />It would be nice to be able to start any mail client and get the same emails. With this, if you want to try a new client, you just start it and you can quickly see if it's good for you.<br /><br />If you use different client for different accounts and don't want to share the emails (not common but it happens), you could simply create a new directory to save the mails. The backend would still be the unified one, but the directory to store the file would be different.<br /><br />For the APIs and implementation, it have to be accepted by the teams of Evolution, Thunderbird and Kmail. It could be based on SQLite but it is also possible to write something more specific.<br /><br />A common backend should not prevent the innovations and distinct features of mail clients. Any clients is free to add custom metadata, as long as those data are not stored is the common backend.<br /><br /><br />pros:<br />-share more code between those project<br />-ability to write a very optimized backend for email (useful in general but also for phones and other small devices)<br />-ability to write small useful apps independant of the mail client (notify how many new mail, update the inbox with small client, etc)<br />-huge improvement for backup<br />-simplify the indexation of mails with tracker/beagle/etc<br /><br />cons:<br />-If you are the writer of a client that needs a lot of data that are not on the backend, you have to deal with two backends for the data. This problem is unlikely to exist (since all clients have nearly all the same features), but I a sure a lot of developers would think it is the case for their software because it is "special" ;)<br />-it has to be multiplatform, which is a pro for me but it also mean it is not trivial to implement<br />
<br />
<b>Attachments</b>:
<br />



No attachments.
]]>
</description>
      <pubDate>Tue, 02-Dec-2008 00:00:00 UTC</pubDate>
      <guid>http://brainstorm.ubuntu.com/item/15943/</guid>
    </item>


  </channel>
</rss>

