<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel rdf:about="http://blogmarks.net/api/marks/tag/cache">
<title>Public marks with tag cache</title>
<description>Public marks with tag cache</description>
<link>http://blogmarks.net/marks/tag/cache</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058571250"/>
<rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058560247"/>
<rdf:li resource="http://blogmarks.net/api/user/RETFU/mark/1058548968"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058556793"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058556806"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1058363653"/>
<rdf:li resource="http://blogmarks.net/api/user/vrossign/mark/1058329588"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058557086"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058557135"/>
<rdf:li resource="http://blogmarks.net/api/user/ERSWeb/mark/1058297371"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058246574"/>
<rdf:li resource="http://blogmarks.net/api/user/br1o/mark/1058557380"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058219296"/>
<rdf:li resource="http://blogmarks.net/api/user/Krome/mark/1058215967"/>
<rdf:li resource="http://blogmarks.net/api/user/pyros/mark/1058214713"/>
<rdf:li resource="http://blogmarks.net/api/user/nicmae/mark/1058209925"/>
<rdf:li resource="http://blogmarks.net/api/user/RETFU/mark/1058187212"/>
<rdf:li resource="http://blogmarks.net/api/user/RETFU/mark/1058187195"/>
<rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058173093"/>
<rdf:li resource="http://blogmarks.net/api/user/JMF/mark/1058128883"/>
<rdf:li resource="http://blogmarks.net/api/user/pyros/mark/1058128286"/>
<rdf:li resource="http://blogmarks.net/api/user/holyver/mark/1058075834"/>
<rdf:li resource="http://blogmarks.net/api/user/ronpish/mark/1058068660"/>
<rdf:li resource="http://blogmarks.net/api/user/camel/mark/1058065074"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1058064729"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058571250">
<title>Overcome Your Caching Conundrums [Server Side Essentials]</title>
<link>http://articles.sitepoint.com/article/overcome-cache-conundrums</link>
<description>ealing with browser caching is a balancing act. On one hand, you aim to minimize load times and bandwidth use by ensuring that images, scripts, and style sheets are cached by your visitors; however, you still want to ensure that they’re accessing the most recent versions of all your files.

In this article, I’ll show you a few methods for controlling how your site’s files are cached by browsers so you can achieve the best of both worlds: maintaining optimal performance while ensuring that any updates are seen immediately, without a hitch by all of your users.</description>
<dc:date>2009-11-03T15:34:24Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>css, image, performance, optimisation, conception web, cache, navigateur</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://articles.sitepoint.com/article/overcome-cache-conundrums"><img border="0" src="http://blogmarks.net/screenshots/2009/11/03/a58cbae6863e4ccdc981f58955828305.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://articles.sitepoint.com/article/overcome-cache-conundrums">Overcome Your Caching Conundrums [Server Side Essentials]</a></h4>
 
by <a href="http://blogmarks.net/user/dzc">dzc</a> 
<p class="description">ealing with browser caching is a balancing act. On one hand, you aim to minimize load times and bandwidth use by ensuring that images, scripts, and style sheets are cached by your visitors; however, you still want to ensure that they’re accessing the most recent versions of all your files.

In this article, I’ll show you a few methods for controlling how your site’s files are cached by browsers so you can achieve the best of both worlds: maintaining optimal performance while ensuring that any updates are seen immediately, without a hitch by all of your users.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/image">image</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimisation">optimisation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/conception%2Bweb">conception web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/navigateur">navigateur</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058571250">Copy</a> | 
<a href="http://blogmarks.net/link/3399935">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058560247">
<title>Cache, HTTP et ressources dynamiques - Carnets de La Grange</title>
<link>http://www.la-grange.net/2009/10/21/http-ressource-bonne-pratique</link>
<description></description>
<dc:date>2009-10-22T13:34:07Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>http, Standard du Web, protocol, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.la-grange.net/2009/10/21/http-ressource-bonne-pratique"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.la-grange.net/2009/10/21/http-ressource-bonne-pratique">Cache, HTTP et ressources dynamiques - Carnets de La Grange</a></h4>
 
by <a href="http://blogmarks.net/user/dzc">dzc</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Standard%2Bdu%2BWeb">Standard du Web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/protocol">protocol</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058560247">Copy</a> | 
<a href="http://blogmarks.net/link/3390968">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/RETFU/mark/1058548968">
<title>MySQL Query cache | dasini.net - Journal d'un expert MySQL</title>
<link>http://dasini.net/blog/2009/10/12/mysql-query-cache/</link>
<description></description>
<dc:date>2009-10-13T07:52:14Z</dc:date>
<dc:author>RETFU</dc:author>
<dc:subject>mysql, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://dasini.net/blog/2009/10/12/mysql-query-cache/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/13/fd805fcf4c5f08cd35ba47c513b175f9.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://dasini.net/blog/2009/10/12/mysql-query-cache/">MySQL Query cache | dasini.net - Journal d'un expert MySQL</a></h4>
 
by <a href="http://blogmarks.net/user/RETFU">RETFU</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058548968">Copy</a> | 
<a href="http://blogmarks.net/link/3382554">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058556793">
<title>Optimisation WordPress – performance, scripts, technique, tools, wordpress | Malaiac Attack</title>
<link>http://www.malaiac.net/465-optimisation-wordpress.html</link>
<description></description>
<dc:date>2009-06-18T06:05:39Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>performance, speed, charge, cache, guide, WP, wordpress, optimization, traffic, tutoriel, apache, load, optimisation, mysql, php</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.malaiac.net/465-optimisation-wordpress.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.malaiac.net/465-optimisation-wordpress.html">Optimisation WordPress – performance, scripts, technique, tools, wordpress | Malaiac Attack</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/speed">speed</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/charge">charge</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/guide">guide</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/WP">WP</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpress">wordpress</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimization">optimization</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/traffic">traffic</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutoriel">tutoriel</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/load">load</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimisation">optimisation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058556793">Copy</a> | 
<a href="http://blogmarks.net/link/3389153">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058556806">
<title>PS CS4: Optimiser des compositions transparent pour fonds unis</title>
<link>http://www.lyxia.org/blog/design/photoshop/ps-cs4-optimiser-des-compositions-transparent-pour-fonds-unis-499</link>
<description></description>
<dc:date>2009-06-15T00:23:40Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>transparent, png, transparence, pipette, cache, graphisme, cs4, photoshop</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.lyxia.org/blog/design/photoshop/ps-cs4-optimiser-des-compositions-transparent-pour-fonds-unis-499"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.lyxia.org/blog/design/photoshop/ps-cs4-optimiser-des-compositions-transparent-pour-fonds-unis-499">PS CS4: Optimiser des compositions transparent pour fonds unis</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/transparent">transparent</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/png">png</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/transparence">transparence</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pipette">pipette</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/graphisme">graphisme</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cs4">cs4</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/photoshop">photoshop</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058556806">Copy</a> | 
<a href="http://blogmarks.net/link/3389163">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Xavier Lacot/mark/1058363653">
<title>sfManagedCachePlugin | Recoursive</title>
<link>http://recoursive.com/blog/sfmanagedcacheplugin</link>
<description>The very point of caching is that it's faster and less resource intensive to deliver cached data than creating it on the fly. With existing cache solutions, when the cached data expires, it has to be refreshed while the user waits. In environments that rely heavily on caching, such behavior has the potential to create thread pileups and other cascading failure scenarios.

This plugin introduces a cache manager : when an expired âge is called, then it is directly served from the cache, and then the cache gets asynchronously refreshed.</description>
<dc:date>2009-06-13T11:22:42Z</dc:date>
<dc:author>Xavier Lacot</dc:author>
<dc:subject>cache, symfony, plugin, manager, performance, optimization</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://recoursive.com/blog/sfmanagedcacheplugin"><img border="0" src="http://blogmarks.net/screenshots/2009/06/13/c0b55ffc522732f8907633221f4d1ec0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://recoursive.com/blog/sfmanagedcacheplugin">sfManagedCachePlugin | Recoursive</a></h4>
 
by <a href="http://blogmarks.net/user/Xavier Lacot">Xavier Lacot</a> 
<p class="description">The very point of caching is that it's faster and less resource intensive to deliver cached data than creating it on the fly. With existing cache solutions, when the cached data expires, it has to be refreshed while the user waits. In environments that rely heavily on caching, such behavior has the potential to create thread pileups and other cascading failure scenarios.

This plugin introduces a cache manager : when an expired âge is called, then it is directly served from the cache, and then the cache gets asynchronously refreshed.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/symfony">symfony</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plugin">plugin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/manager">manager</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimization">optimization</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058363653">Copy</a> | 
<a href="http://blogmarks.net/link/3229938">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/vrossign/mark/1058329588">
<title>Caching Tutorial for Web Authors and Webmasters</title>
<link>http://www.mnot.net/cache_docs/</link>
<description></description>
<dc:date>2009-05-19T11:54:41Z</dc:date>
<dc:author>vrossign</dc:author>
<dc:subject>web, caching, cache, headers, apache, performances</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.mnot.net/cache_docs/"><img border="0" src="http://blogmarks.net/screenshots/2009/05/19/22cfcc417810dca858c9b5fca75a60f5.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.mnot.net/cache_docs/">Caching Tutorial for Web Authors and Webmasters</a></h4>
 
by <a href="http://blogmarks.net/user/vrossign">vrossign</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/45840">25 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/caching">caching</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/headers">headers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performances">performances</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058329588">Copy</a> | 
<a href="http://blogmarks.net/link/45840">React (1)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058557086">
<title>Cache central des bibliothèques javascript —Performance web</title>
<link>http://performance.survol.fr/2009/02/cache-central-des-bibliotheques-javascript/</link>
<description></description>
<dc:date>2009-05-09T11:24:55Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>cache, library, conseil, optimisation, script, jQuery, google, javascript, cdn, performance, yui, bibliothèque</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://performance.survol.fr/2009/02/cache-central-des-bibliotheques-javascript/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://performance.survol.fr/2009/02/cache-central-des-bibliotheques-javascript/">Cache central des bibliothèques javascript —Performance web</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/library">library</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/conseil">conseil</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimisation">optimisation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/script">script</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/jQuery">jQuery</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cdn">cdn</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/yui">yui</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/biblioth%25C3%25A8que">bibliothèque</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058557086">Copy</a> | 
<a href="http://blogmarks.net/link/3389333">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058557135">
<title>Coder en CSS plus rapidement, plus intelligemment | Le Blog de LunaWeb</title>
<link>http://www.lunaweb.fr/blog/coder-en-css-plus-rapidement-plus-intelligemment/</link>
<description></description>
<dc:date>2009-05-05T22:34:15Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>php, css, gzip, grille, align, classe, csscacheer, cache, compression</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.lunaweb.fr/blog/coder-en-css-plus-rapidement-plus-intelligemment/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.lunaweb.fr/blog/coder-en-css-plus-rapidement-plus-intelligemment/">Coder en CSS plus rapidement, plus intelligemment | Le Blog de LunaWeb</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gzip">gzip</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/grille">grille</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/align">align</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/classe">classe</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/csscacheer">csscacheer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/compression">compression</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058557135">Copy</a> | 
<a href="http://blogmarks.net/link/3389359">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ERSWeb/mark/1058297371">
<title>Web Cache | Gear6</title>
<link>http://www.gear6.com/web-cache/tech-specs</link>
<description>Gear6 Web Cache is a Memcached protocol-compliant solution that scales and accelerates web applications, reduces memory footprint, enhances availability and implements comprehensive Memcached management features. Designed to work with all popular memcache clients, Gear6 Web Cache integrates seamlessly into existing deployments and immediately provides a scalable, high density caching solution for your web application environment.</description>
<dc:date>2009-04-24T16:16:08Z</dc:date>
<dc:author>ERSWeb</dc:author>
<dc:subject>web, work, cache, memcached</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.gear6.com/web-cache/tech-specs"><img border="0" src="http://blogmarks.net/screenshots/2009/04/24/6757a8ae49fcadf7d28dff108291a7df.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.gear6.com/web-cache/tech-specs">Web Cache | Gear6</a></h4>
 
by <a href="http://blogmarks.net/user/ERSWeb">ERSWeb</a> 
<p class="description">Gear6 Web Cache is a Memcached protocol-compliant solution that scales and accelerates web applications, reduces memory footprint, enhances availability and implements comprehensive Memcached management features. Designed to work with all popular memcache clients, Gear6 Web Cache integrates seamlessly into existing deployments and immediately provides a scalable, high density caching solution for your web application environment.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/work">work</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memcached">memcached</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058297371">Copy</a> | 
<a href="http://blogmarks.net/link/3173850">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058246574">
<title>Installing APC in Windows - MoodleDocs</title>
<link>http://docs.moodle.org/en/Installing_APC_in_Windows</link>
<description>APC (Alternative PHP Cache) is a PHP opcode cache. It stores PHP pages in RAM and reduces hard disk activity. This makes a real difference to the performance in Moodle, and you should be able to achieve a 50% increase in system capacity and your CPU will be 50% less busy.

This guide is for installation of APC on a Windows server. The instructions have been tested on a Windows 2003 server, and they should also be applicable if you are using Windows XP as a test server. </description>
<dc:date>2009-03-22T05:17:05Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>performance, php, windows, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://docs.moodle.org/en/Installing_APC_in_Windows"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://docs.moodle.org/en/Installing_APC_in_Windows">Installing APC in Windows - MoodleDocs</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
<p class="description">APC (Alternative PHP Cache) is a PHP opcode cache. It stores PHP pages in RAM and reduces hard disk activity. This makes a real difference to the performance in Moodle, and you should be able to achieve a 50% increase in system capacity and your CPU will be 50% less busy.

This guide is for installation of APC on a Windows server. The instructions have been tested on a Windows 2003 server, and they should also be applicable if you are using Windows XP as a test server. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/windows">windows</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058246574">Copy</a> | 
<a href="http://blogmarks.net/link/3132186">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/br1o/mark/1058557380">
<title>IE6/Win, background image on &lt;a&gt;, cache=‘check every visit’: flicker!</title>
<link>http://www.brunildo.org/test/IEAbackima.html</link>
<description></description>
<dc:date>2009-03-11T23:42:58Z</dc:date>
<dc:author>br1o</dc:author>
<dc:subject>ie6, images, hacks, browsers, cache, bugs, webstandards, bug, fix, flicker, bugfix, css, design, image</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.brunildo.org/test/IEAbackima.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.brunildo.org/test/IEAbackima.html">IE6/Win, background image on &lt;a&gt;, cache=‘check every visit’: flicker!</a></h4>
 
by <a href="http://blogmarks.net/user/br1o">br1o</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ie6">ie6</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/images">images</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hacks">hacks</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/browsers">browsers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bugs">bugs</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webstandards">webstandards</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bug">bug</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fix">fix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flicker">flicker</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bugfix">bugfix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/design">design</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/image">image</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058557380">Copy</a> | 
<a href="http://blogmarks.net/link/3389497">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/srcmax/mark/1058219296">
<title>BackupUrl.com - Create a cached copy of any url!</title>
<link>http://backupurl.com/create.php</link>
<description></description>
<dc:date>2009-02-23T15:33:08Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>backup, archive, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://backupurl.com/create.php"><img border="0" src="http://blogmarks.net/screenshots/2009/02/23/f1ac302d4be54ea9caa0d6264494630d.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://backupurl.com/create.php">BackupUrl.com - Create a cached copy of any url!</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3108218">2 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/backup">backup</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/archive">archive</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058219296">Copy</a> | 
<a href="http://blogmarks.net/link/3108218">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Krome/mark/1058215967">
<title>3n's db-script-cache at master - GitHub</title>
<link>http://github.com/3n/db-script-cache/tree/master</link>
<description>Ian Collins has created DBScriptCache, a JavaScript program that &quot;automatically caches script files in the browser's HTML5 client-side database. Rather than including your scripts using script tags, you include them using this script. The first time a user views the page the scripts will be pulled into the db and stored. On subsequent visits the scripts will be loaded from the db cache and not from your server. The script will continue to come from the cache until you supply a new version number or change the name of the script.&quot;</description>
<dc:date>2009-02-20T12:50:38Z</dc:date>
<dc:author>Krome</dc:author>
<dc:subject>webdev, cache, javascript, html5</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://github.com/3n/db-script-cache/tree/master"><img border="0" src="http://blogmarks.net/screenshots/2009/02/20/f7389c45ec64f35338381fea3255a6a5.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://github.com/3n/db-script-cache/tree/master">3n's db-script-cache at master - GitHub</a></h4>
 
by <a href="http://blogmarks.net/user/Krome">Krome</a> 
<p class="description">Ian Collins has created DBScriptCache, a JavaScript program that "automatically caches script files in the browser's HTML5 client-side database. Rather than including your scripts using script tags, you include them using this script. The first time a user views the page the scripts will be pulled into the db and stored. On subsequent visits the scripts will be loaded from the db cache and not from your server. The script will continue to come from the cache until you supply a new version number or change the name of the script."</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdev">webdev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html5">html5</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058215967">Copy</a> | 
<a href="http://blogmarks.net/link/3105585">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/pyros/mark/1058214713">
<title>Tokyo Cabinet: a modern implementation of DBM</title>
<link>http://tokyocabinet.sourceforge.net/index.html</link>
<description></description>
<dc:date>2009-02-19T11:10:52Z</dc:date>
<dc:author>pyros</dc:author>
<dc:subject>tokyo, cabinet, database, hash, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://tokyocabinet.sourceforge.net/index.html"><img border="0" src="http://blogmarks.net/screenshots/2009/02/19/f349119b3954201dd3165170eaf08f20.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://tokyocabinet.sourceforge.net/index.html">Tokyo Cabinet: a modern implementation of DBM</a></h4>
 
by <a href="http://blogmarks.net/user/pyros">pyros</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2933748">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tokyo">tokyo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cabinet">cabinet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hash">hash</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058214713">Copy</a> | 
<a href="http://blogmarks.net/link/2933748">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/nicmae/mark/1058209925">
<title>Cache it! Solve PHP Performance Problems [PHP &amp; MySQL Tutorials]</title>
<link>http://www.sitepoint.com/article/caching-php-performance/4/</link>
<description>caching</description>
<dc:date>2009-02-15T21:54:09Z</dc:date>
<dc:author>nicmae</dc:author>
<dc:subject>php, mysql, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.sitepoint.com/article/caching-php-performance/4/"><img border="0" src="http://blogmarks.net/screenshots/2009/02/15/e9a051c3403ab56d45ab3c9cd2c032fb.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.sitepoint.com/article/caching-php-performance/4/">Cache it! Solve PHP Performance Problems [PHP &amp; MySQL Tutorials]</a></h4>
 
by <a href="http://blogmarks.net/user/nicmae">nicmae</a> 
<p class="description">caching</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058209925">Copy</a> | 
<a href="http://blogmarks.net/link/3100493">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/RETFU/mark/1058187212">
<title>How To Set Up A Caching Reverse Proxy With Squid 2.6 On Debian Etch | HowtoForge - Linux Howtos and Tutorials</title>
<link>http://www.howtoforge.com/how-to-set-up-a-caching-reverse-proxy-with-squid-2.6-on-debian-etch</link>
<description></description>
<dc:date>2009-02-06T14:26:14Z</dc:date>
<dc:author>RETFU</dc:author>
<dc:subject>squid, proxy, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.howtoforge.com/how-to-set-up-a-caching-reverse-proxy-with-squid-2.6-on-debian-etch"><img border="0" src="http://blogmarks.net/screenshots/2009/02/06/9b03f6b179152e7fb7a931b58a855e01.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.howtoforge.com/how-to-set-up-a-caching-reverse-proxy-with-squid-2.6-on-debian-etch">How To Set Up A Caching Reverse Proxy With Squid 2.6 On Debian Etch | HowtoForge - Linux Howtos and Tutorials</a></h4>
 
by <a href="http://blogmarks.net/user/RETFU">RETFU</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3041247">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/squid">squid</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/proxy">proxy</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058187212">Copy</a> | 
<a href="http://blogmarks.net/link/3041247">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/RETFU/mark/1058187195">
<title>squid : Optimising Web Delivery</title>
<link>http://www.squid-cache.org/</link>
<description></description>
<dc:date>2009-02-06T14:26:07Z</dc:date>
<dc:author>RETFU</dc:author>
<dc:subject>proxy, cache, squid</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.squid-cache.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/02/06/f4d375d7a07ee003d29484143b1be447.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.squid-cache.org/">squid : Optimising Web Delivery</a></h4>
 
by <a href="http://blogmarks.net/user/RETFU">RETFU</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/126197">7 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/proxy">proxy</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/squid">squid</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058187195">Copy</a> | 
<a href="http://blogmarks.net/link/126197">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058173093">
<title>MySQL Query Cache, WP-Cache, APC, Memcache - What to choose « Abhi’s Weblog</title>
<link>http://abhinavsingh.com/blog/2009/01/mysql-query-cache-wp-cache-apc-memcache-what-to-choose/</link>
<description></description>
<dc:date>2009-01-27T11:36:45Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>mysql, php, cache, optimisation</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://abhinavsingh.com/blog/2009/01/mysql-query-cache-wp-cache-apc-memcache-what-to-choose/"><img border="0" src="http://blogmarks.net/screenshots/2009/01/27/95d8e3f36b8eb038768b8c7bc218a84c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://abhinavsingh.com/blog/2009/01/mysql-query-cache-wp-cache-apc-memcache-what-to-choose/">MySQL Query Cache, WP-Cache, APC, Memcache - What to choose « Abhi’s Weblog</a></h4>
 
by <a href="http://blogmarks.net/user/dzc">dzc</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimisation">optimisation</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058173093">Copy</a> | 
<a href="http://blogmarks.net/link/3067808">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/JMF/mark/1058128883">
<title>Enhance PHP session management</title>
<link>http://kevin.vanzonneveld.net/techblog/article/enhance_php_session_management/</link>
<description></description>
<dc:date>2008-12-14T17:12:05Z</dc:date>
<dc:author>JMF</dc:author>
<dc:subject>php, memcache, optimisation, cache, sessions</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://kevin.vanzonneveld.net/techblog/article/enhance_php_session_management/"><img border="0" src="http://blogmarks.net/screenshots/2008/12/15/66125025f522c51bdd6e698cc5ad88b1.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://kevin.vanzonneveld.net/techblog/article/enhance_php_session_management/">Enhance PHP session management</a></h4>
 
by <a href="http://blogmarks.net/user/JMF">JMF</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3029568">1 other(s)</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memcache">memcache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimisation">optimisation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sessions">sessions</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058128883">Copy</a> | 
<a href="http://blogmarks.net/link/3029568">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/pyros/mark/1058128286">
<title>nkallen's cache-money at master — GitHub</title>
<link>http://www.github.com/nkallen/cache-money/tree/master</link>
<description></description>
<dc:date>2008-12-14T10:12:13Z</dc:date>
<dc:author>pyros</dc:author>
<dc:subject>ruby, activerecord, cache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.github.com/nkallen/cache-money/tree/master"><img border="0" src="http://blogmarks.net/screenshots/2008/12/14/7ce8df60f8da3e10576944736591d2e6.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.github.com/nkallen/cache-money/tree/master">nkallen's cache-money at master — GitHub</a></h4>
 
by <a href="http://blogmarks.net/user/pyros">pyros</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ruby">ruby</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/activerecord">activerecord</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058128286">Copy</a> | 
<a href="http://blogmarks.net/link/3029037">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/holyver/mark/1058075834">
<title>reallysimplehistory - Google Code</title>
<link>http://code.google.com/p/reallysimplehistory/</link>
<description>Really Simple History is a lightweight JavaScript library for the management of bookmarking and browser history in Ajax/DHTML applications. RSH serializes application data in an internal JavaScript cache so that bookmarks and the back button can be used to return your application to an earlier state.

Originally developed by Brad Neuberg in 2005, RSH has won a large user base for its simplicity, ease of use and lack of dependency on any specific Ajax framework. It's written in plain old JavaScript and can be included on any site according to the terms of its BSD license.

In September 2007, Brian Dillard of Pathfinder Development came on board as maintainer and ongoing code steward for the project. A new version, with support for additional modern browsers (IE7, Safari, Opera), was released as RSH 0.6 on December 3, 2007. </description>
<dc:date>2008-11-30T14:32:14Z</dc:date>
<dc:author>holyver</dc:author>
<dc:subject>history, cache, application, javascript, google, library, ajax, code</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/p/reallysimplehistory/"><img border="0" src="http://blogmarks.net/screenshots/2008/11/30/cdaa3d50d307f573f57867cd8460ba08.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/p/reallysimplehistory/">reallysimplehistory - Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/holyver">holyver</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2506116">1 other(s)</a> 
<p class="description">Really Simple History is a lightweight JavaScript library for the management of bookmarking and browser history in Ajax/DHTML applications. RSH serializes application data in an internal JavaScript cache so that bookmarks and the back button can be used to return your application to an earlier state.

Originally developed by Brad Neuberg in 2005, RSH has won a large user base for its simplicity, ease of use and lack of dependency on any specific Ajax framework. It's written in plain old JavaScript and can be included on any site according to the terms of its BSD license.

In September 2007, Brian Dillard of Pathfinder Development came on board as maintainer and ongoing code steward for the project. A new version, with support for additional modern browsers (IE7, Safari, Opera), was released as RSH 0.6 on December 3, 2007. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/history">history</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/application">application</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/javascript">javascript</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/library">library</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ajax">ajax</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/code">code</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058075834">Copy</a> | 
<a href="http://blogmarks.net/link/2506116">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ronpish/mark/1058068660">
<title>Flex and Flash Developer - Jesse Warden dot Kizz-ohm » Blog Archive » Writing a Caching Engine for Flash Player</title>
<link>http://jessewarden.com/2008/11/writing-a-caching-engine-for-flash-player.html</link>
<description></description>
<dc:date>2008-11-23T15:09:32Z</dc:date>
<dc:author>ronpish</dc:author>
<dc:subject>flash, flex, cache, as3</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://jessewarden.com/2008/11/writing-a-caching-engine-for-flash-player.html"><img border="0" src="http://blogmarks.net/screenshots/2008/11/23/7ca73d503cb0940a783d51b1de951d83.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://jessewarden.com/2008/11/writing-a-caching-engine-for-flash-player.html">Flex and Flash Developer - Jesse Warden dot Kizz-ohm » Blog Archive » Writing a Caching Engine for Flash Player</a></h4>
 
by <a href="http://blogmarks.net/user/ronpish">ronpish</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flash">flash</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flex">flex</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/as3">as3</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058068660">Copy</a> | 
<a href="http://blogmarks.net/link/2977060">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/camel/mark/1058065074">
<title>CloudFront : Amazon lance son service de CDN (Content Delivery Network)</title>
<link>http://www.haute-disponibilite.net/2008/11/18/cloudfront-amazon-service-de-cdn/</link>
<description>On me pose souvent la question du coût des solutions de CDN Akamai pour gérer la disponibilité d’un site. Et en général le problème majeur avec cet acteur vient des frais de fonctionnement et de mise en service. En effet au delà de l’engagement contractuel sur la durée la mise en place d’une solution Akamai est relativement coûteuse pour des “petits” acteurs.

Cette annonce d’Amazon est donc une très bonne nouvelle pour le segment des sites de taille moyenne, trop petits pour négocier avec Akamai et gérant déjà un trafic suffisamment important pour être obligé de mettre en place des solutions de cache distribués, des CDN.</description>
<dc:date>2008-11-19T21:01:34Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>cache, cdn, amazon, akamai</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.haute-disponibilite.net/2008/11/18/cloudfront-amazon-service-de-cdn/"><img border="0" src="http://blogmarks.net/screenshots/2008/11/19/79aeb3ee3f20917bc626af272ecc3717.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.haute-disponibilite.net/2008/11/18/cloudfront-amazon-service-de-cdn/">CloudFront : Amazon lance son service de CDN (Content Delivery Network)</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
<p class="description">On me pose souvent la question du coût des solutions de CDN Akamai pour gérer la disponibilité d’un site. Et en général le problème majeur avec cet acteur vient des frais de fonctionnement et de mise en service. En effet au delà de l’engagement contractuel sur la durée la mise en place d’une solution Akamai est relativement coûteuse pour des “petits” acteurs.

Cette annonce d’Amazon est donc une très bonne nouvelle pour le segment des sites de taille moyenne, trop petits pour négocier avec Akamai et gérant déjà un trafic suffisamment important pour être obligé de mettre en place des solutions de cache distribués, des CDN.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cdn">cdn</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/amazon">amazon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/akamai">akamai</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058065074">Copy</a> | 
<a href="http://blogmarks.net/link/2973537">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1058064729">
<title>Things Caches Do</title>
<link>http://tomayko.com/writings/things-caches-do</link>
<description></description>
<dc:date>2008-11-19T14:40:57Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>cache, http</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://tomayko.com/writings/things-caches-do"><img border="0" src="http://blogmarks.net/screenshots/2008/11/19/ca1e22c71a9e262fea3ed84da576a32e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://tomayko.com/writings/things-caches-do">Things Caches Do</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/http">http</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058064729">Copy</a> | 
<a href="http://blogmarks.net/link/2973193">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>