<?xml version="1.0"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>CKAN: Ticket #1189: Spideroak support in CKAN Storage</title>
    <link>http://localhost/ticket/1189</link>
    <description>&lt;p&gt;
&lt;a class="ext-link" href="http://spideroak.com"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;Spideroak&lt;/a&gt; is a bulk storage platform by a company that releases quite a lot of &lt;a class="ext-link" href="https://spideroak.com/code"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;free software&lt;/a&gt;, has an extensive &lt;a class="ext-link" href="https://spideroak.com/diy/"&gt;&lt;span class="icon"&gt;​&lt;/span&gt;developer API&lt;/a&gt; with pricing of $10/100GB/month.
&lt;/p&gt;
&lt;p&gt;
The data store is optimised for bulk data storage and retrieval. This is the kind of use case that CKAN packages require. We don't need low latency. We are after low cost, high reliability solution.
&lt;/p&gt;
</description>
    <language>en-us</language>
    <image>
      <title>CKAN</title>
      <url>http://assets.okfn.org/p/ckan/img/ckan_logo_shortname.png</url>
      <link>http://localhost/ticket/1189</link>
    </image>
    <generator>Trac 0.12.3</generator>
    <item>
      
        <dc:creator>thejimmyg</dc:creator>

      <pubDate>Tue, 06 Dec 2011 12:07:07 GMT</pubDate>
      <title>status changed; resolution set</title>
      <link>http://localhost/ticket/1189#comment:1</link>
      <guid isPermaLink="false">http://localhost/ticket/1189#comment:1</guid>
      <description>
          &lt;ul&gt;
            &lt;li&gt;&lt;strong&gt;status&lt;/strong&gt;
                changed from &lt;em&gt;new&lt;/em&gt; to &lt;em&gt;closed&lt;/em&gt;
            &lt;/li&gt;
            &lt;li&gt;&lt;strong&gt;resolution&lt;/strong&gt;
                set to &lt;em&gt;invalid&lt;/em&gt;
            &lt;/li&gt;
          &lt;/ul&gt;
        &lt;p&gt;
Closing this ticket in line with ticketing policy since it is over 6 months old. If someone would like to develop an extension that uses spideroak as a back end we can look at it again.
&lt;/p&gt;
      </description>
      <category>Ticket</category>
    </item>
 </channel>
</rss>