<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0">
  <channel>
    <title><![CDATA[cache xml/rss]]></title>
    <link>http://ideas.plings.info/ideatorrent/item/13/</link>
    <description><![CDATA[The data we have in plings continues to increase day by day.  At some point in the future we will have to cache the information locally or <br />maybe even on the plings server itself.  This needs careful consideration as we don't want out date or incorrect information reaching users.<br /><br /><br /><br />
<br />


<b>[0 votes] Solution #1: use apache etags</b>
<br />

<br />
<br />



<b>[1 votes] Solution #2: add gzip support</b>
<br />

<br />
<br />



]]></description>

    <language>en-us</language>
    <pubDate>Tue, 18 Aug 2009 19:46:43 +0100</pubDate>
    <lastBuildDate>Mon, 21 Jun 2010 11:26:00 +0100</lastBuildDate>
    <generator>QAPoll module</generator>
    <guid isPermaLink="true">http://ideas.plings.info/ideatorrent/idea/13/</guid>
        <item>
  <title>Comment from kaerast</title>
  <description><![CDATA[Most, if not all clients, support gzip and Etags and other caching technologies.  The two solutions are not mutually exclusive.  If this is really a bottleneck then the first step would be to implement Etags and Expires headers and just shove a reverse caching proxy infront of the APIs.  Varnish would be great for this, especially if there's a spare dedicated box; Apache, Squid and Nginx are alternatives.<br /><br />It might be worth considering adding Memcache or another PHP caching technology (APC) too.]]></description>
  <pubDate>Mon, 21 Jun 2010 11:26:00 +0100</pubDate>
</item>
      </channel>
</rss>
