<?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/search/cache">
<title>Public marks with search cache</title>
<description>Public marks with search cache</description>
<link>http://blogmarks.net/marks/search/cache</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/mozkart/mark/1058564957"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058562239"/>
<rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058560247"/>
<rdf:li resource="http://blogmarks.net/api/user/srcmax/mark/1058551000"/>
<rdf:li resource="http://blogmarks.net/api/user/RETFU/mark/1058548968"/>
<rdf:li resource="http://blogmarks.net/api/user/fxbis/mark/1058542954"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058513466"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058513456"/>
<rdf:li resource="http://blogmarks.net/api/user/danijelzi/mark/1058496976"/>
<rdf:li resource="http://blogmarks.net/api/user/danijelzi/mark/1058496064"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058486058"/>
<rdf:li resource="http://blogmarks.net/api/user/Neewok/mark/1058484626"/>
<rdf:li resource="http://blogmarks.net/api/user/nicolargo/mark/1058484162"/>
<rdf:li resource="http://blogmarks.net/api/user/mozkart/mark/1058481895"/>
<rdf:li resource="http://blogmarks.net/api/user/paulantoinem/mark/1058488623"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058462528"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058461266"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547923"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058547924"/>
<rdf:li resource="http://blogmarks.net/api/user/kruty/mark/1058427027"/>
<rdf:li resource="http://blogmarks.net/api/user/kruty/mark/1058427026"/>
<rdf:li resource="http://blogmarks.net/api/user/kasi77/mark/1058417147"/>
<rdf:li resource="http://blogmarks.net/api/user/Xavier Lacot/mark/1058363653"/>
<rdf:li resource="http://blogmarks.net/api/user/tisienpo/mark/1058345645"/>
<rdf:li resource="http://blogmarks.net/api/user/mozkart/mark/1058338914"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/mozkart/mark/1058564957">
<title>WordPress MU « WordPress Codex</title>
<link>http://codex.wordpress.org/WordPressMU</link>
<description>Pour cela, il suffit juste de changer 4 paramètres de PHP et pour y parvenir nous allons créé/édité le fichier .htaccess à la racine de votre FTP. (dans le dossier WWW)

Et on va y insérer les lignes:

SetEnv REGISTER_GLOBALS 0
SetEnv ZEND_OPTIMIZER 1
SetEnv MAGIC_QUOTES 0
SetEnv PHP_VER 5

Autrement dit, on désactive les directives PHP magic quotes, register globals qui n’apportent rien à WordPress.
On passe à PHP5 (qui offre une meilleure comptabilité avec les extensions) et on active le module PHP Zend Optimiser, ainsi le code PHP sera optimisé et les traitements récurrents seront mis en cache.</description>
<dc:date>2009-10-27T22:23:58Z</dc:date>
<dc:author>mozkart</dc:author>
<dc:subject>wordpress</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://codex.wordpress.org/WordPressMU"><img border="0" src="http://blogmarks.net/screenshots/2009/10/27/d0c426c79c5027152d014cd35a402b92.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://codex.wordpress.org/WordPressMU">WordPress MU « WordPress Codex</a></h4>
 
by <a href="http://blogmarks.net/user/mozkart">mozkart</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1314611">1 other(s)</a> 
<p class="description">Pour cela, il suffit juste de changer 4 paramètres de PHP et pour y parvenir nous allons créé/édité le fichier .htaccess à la racine de votre FTP. (dans le dossier WWW)

Et on va y insérer les lignes:

SetEnv REGISTER_GLOBALS 0
SetEnv ZEND_OPTIMIZER 1
SetEnv MAGIC_QUOTES 0
SetEnv PHP_VER 5

Autrement dit, on désactive les directives PHP magic quotes, register globals qui n’apportent rien à WordPress.
On passe à PHP5 (qui offre une meilleure comptabilité avec les extensions) et on active le module PHP Zend Optimiser, ainsi le code PHP sera optimisé et les traitements récurrents seront mis en cache.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpress">wordpress</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058564957">Copy</a> | 
<a href="http://blogmarks.net/link/1314611">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058562239">
<title>Time/Weather Desktop on Flickr - Photo Sharing!</title>
<link>http://www.flickr.com/photos/bopuc/4039178260/</link>
<description>&lt;blockquote&gt;&lt;p&gt;Well, most of the work is done by Earthdesk and GeekTool 3.&lt;/p&gt;&lt;p&gt;Earthdesk is set to Natural Color, Equirectangular projection, Natural Color, Real Moonlight, centered on Vienna, Background: Starfield. Zoom 80%, Clouds 80%, Brightness 80%.&lt;/p&gt;&lt;p&gt;In GeekTool, the times and the weathers are all separate Shell &quot;geeklets&quot;.&lt;/p&gt;&lt;p&gt;Times are generated by running shell commands like&lt;/p&gt;&lt;p&gt;env TZ=Asia/Tokyo date &quot; %l:%M %p&quot;&lt;/p&gt;&lt;p&gt;every 20 seconds&lt;/p&gt;&lt;p&gt;The weather is the tricky part. The way I am doing it now, if I am not careful, gets me throttled for too many concurrent requests to the wunderground.com API server. It also fails badly if I am disconnected, so I will need to do it differently.&lt;/p&gt;&lt;p&gt;FWIW: I have a PHP script which I run as separate Shell Geeklets. I invoke it with the name of the city I want. It then hits wunderground and gets back an XML stream of the local weather, which I parse, format and echo. (the way I'd change this is run the script from cron, with a 30 second wait between requests, and cache the results locally, which I would then call from the Shell Geeklets)&lt;/p&gt;&lt;p&gt;From there it's just a question of setting fonts, sizes, colors and moving the little Geeklet boxes around as you want them.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-24T15:00:49Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>semanticdesktop, meteo, geek</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.flickr.com/photos/bopuc/4039178260/"><img border="0" src="http://blogmarks.net/screenshots/2009/10/24/5639bd0d870c47d4c396495e456804ec.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.flickr.com/photos/bopuc/4039178260/">Time/Weather Desktop on Flickr - Photo Sharing!</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Well, most of the work is done by Earthdesk and GeekTool 3.</p><p>Earthdesk is set to Natural Color, Equirectangular projection, Natural Color, Real Moonlight, centered on Vienna, Background: Starfield. Zoom 80%, Clouds 80%, Brightness 80%.</p><p>In GeekTool, the times and the weathers are all separate Shell "geeklets".</p><p>Times are generated by running shell commands like</p><p>env TZ=Asia/Tokyo date " %l:%M %p"</p><p>every 20 seconds</p><p>The weather is the tricky part. The way I am doing it now, if I am not careful, gets me throttled for too many concurrent requests to the wunderground.com API server. It also fails badly if I am disconnected, so I will need to do it differently.</p><p>FWIW: I have a PHP script which I run as separate Shell Geeklets. I invoke it with the name of the city I want. It then hits wunderground and gets back an XML stream of the local weather, which I parse, format and echo. (the way I'd change this is run the script from cron, with a 30 second wait between requests, and cache the results locally, which I would then call from the Shell Geeklets)</p><p>From there it's just a question of setting fonts, sizes, colors and moving the little Geeklet boxes around as you want them.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/semanticdesktop">semanticdesktop</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/meteo">meteo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geek">geek</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058562239">Copy</a> | 
<a href="http://blogmarks.net/link/3392654">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/srcmax/mark/1058551000">
<title>faq - swfobject - SWFObject FAQ - Project Hosting on Google Code</title>
<link>http://code.google.com/p/swfobject/wiki/faq#16._Why_does_Firefox_load_my_SWF_twice?</link>
<description>&lt;blockquote&gt;
&lt;p&gt;16. Why does Firefox load my SWF twice?&lt;/p&gt;
&lt;p&gt;Firefox 3 has a known issue that sometimes causes a swf to be 'double initialized'. The problem appears to be fixed in their codebase, but has not been released yet. See the following bugs for more details: bug 438830 and bug 445599.&lt;/p&gt;
&lt;p&gt;Or, if you have &quot;Disable cache&quot; selected in your Firefox Web Developer Toolbar extension a double load will occur.&lt;/p&gt;
&lt;/blockquote&gt;</description>
<dc:date>2009-10-15T13:45:57Z</dc:date>
<dc:author>srcmax</dc:author>
<dc:subject>firefox, swfobject, bug</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/p/swfobject/wiki/faq#16._Why_does_Firefox_load_my_SWF_twice?"><img border="0" src="http://blogmarks.net/screenshots/2009/10/15/03173ac811fbad6b46c8e77c94609fff.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/p/swfobject/wiki/faq#16._Why_does_Firefox_load_my_SWF_twice?">faq - swfobject - SWFObject FAQ - Project Hosting on Google Code</a></h4>
 
by <a href="http://blogmarks.net/user/srcmax">srcmax</a> 
<div class="description"><blockquote>
<p>16. Why does Firefox load my SWF twice?</p>
<p>Firefox 3 has a known issue that sometimes causes a swf to be 'double initialized'. The problem appears to be fixed in their codebase, but has not been released yet. See the following bugs for more details: bug 438830 and bug 445599.</p>
<p>Or, if you have "Disable cache" selected in your Firefox Web Developer Toolbar extension a double load will occur.</p>
</blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/firefox">firefox</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/swfobject">swfobject</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bug">bug</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058551000">Copy</a> | 
<a href="http://blogmarks.net/link/3384254">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/fxbis/mark/1058542954">
<title>Résultats Google Recherche d'images correspondant à http://static.vitalsenior.fr/media/catalog/product/cache/1/image/260x/5e06319eda06f020e43594a9c230972d/f/i/file_5_26.jpg</title>
<link>http://images.google.fr/imgres?imgurl=http://static.vitalsenior.fr/media/catalog/product/cache/1/image/260x/5e06319eda06f020e43594a9c230972d/f/i/file_5_26.jpg&amp;imgrefurl=http://www.vitalsenior.fr/pilulier-anabox-arc-en-ciel.html&amp;usg=__XZDS0AW4DFopg8ooS96Pl</link>
<description></description>
<dc:date>2009-10-08T20:05:16Z</dc:date>
<dc:author>fxbis</dc:author>
<dc:subject>pilulier</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://images.google.fr/imgres?imgurl=http://static.vitalsenior.fr/media/catalog/product/cache/1/image/260x/5e06319eda06f020e43594a9c230972d/f/i/file_5_26.jpg&amp;imgrefurl=http://www.vitalsenior.fr/pilulier-anabox-arc-en-ciel.html&amp;usg=__XZDS0AW4DFopg8ooS96Pl"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://images.google.fr/imgres?imgurl=http://static.vitalsenior.fr/media/catalog/product/cache/1/image/260x/5e06319eda06f020e43594a9c230972d/f/i/file_5_26.jpg&amp;imgrefurl=http://www.vitalsenior.fr/pilulier-anabox-arc-en-ciel.html&amp;usg=__XZDS0AW4DFopg8ooS96Pl">Résultats Google Recherche d'images correspondant à http://static.vitalsenior.fr/media/catalog/product/cache/1/image/260x/5e06319eda06f020e43594a9c230972d/f/i/file_5_26.jpg</a></h4>
 
by <a href="http://blogmarks.net/user/fxbis">fxbis</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/pilulier">pilulier</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058542954">Copy</a> | 
<a href="http://blogmarks.net/link/3377522">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058513466">
<title>Surfin’ Safari - Blog Archive » WebKit Page Cache II – The unload Event</title>
<link>http://webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/</link>
<description>&lt;blockquote&gt;&lt;p&gt;In this article I’d like to talk more about unload event handlers, why they prevent pages from going into the Page Cache, and what can be done to make things better.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-23T02:31:05Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>safari, webkit, httpput</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/23/45eca708cf324a0f75cfa0c0f44ef738.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://webkit.org/blog/516/webkit-page-cache-ii-the-unload-event/">Surfin’ Safari - Blog Archive » WebKit Page Cache II – The unload Event</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>In this article I’d like to talk more about unload event handlers, why they prevent pages from going into the Page Cache, and what can be done to make things better.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/safari">safari</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webkit">webkit</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/httpput">httpput</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058513466">Copy</a> | 
<a href="http://blogmarks.net/link/3350531">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058513456">
<title>Surfin’ Safari - Blog Archive » WebKit Page Cache I – The Basics</title>
<link>http://webkit.org/blog/427/webkit-page-cache-i-the-basics/</link>
<description>&lt;blockquote&gt;&lt;p&gt;This is the first of two posts that will center around a modern browser engine feature that doesn’t usually get a lot of press: The Page Cache.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-09-23T02:08:59Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>safari, webkit, http</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://webkit.org/blog/427/webkit-page-cache-i-the-basics/"><img border="0" src="http://blogmarks.net/screenshots/2009/09/23/48f5ffa6ddd364ce0d4d907a84b13e11.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://webkit.org/blog/427/webkit-page-cache-i-the-basics/">Surfin’ Safari - Blog Archive » WebKit Page Cache I – The Basics</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This is the first of two posts that will center around a modern browser engine feature that doesn’t usually get a lot of press: The Page Cache.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/safari">safari</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webkit">webkit</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=1058513456">Copy</a> | 
<a href="http://blogmarks.net/link/3350527">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/danijelzi/mark/1058496976">
<title>Intel Core i7 860 CPU Now Available</title>
<link>http://computermonger.com/intel-core-i7-860.html</link>
<description>The Intel Core i7 860, the company’s new 45nm quad core processor, can be ordered now at Newegg. The Core i7 860 “Lynnfield” Socket LGA1156 chip is clocked at 2.8GHz. It has 8MB of cache and a TDP of 95W. The i7 860, retail model BX80605I7860, is priced at $299.99 with free shipping.</description>
<dc:date>2009-09-08T11:59:45Z</dc:date>
<dc:author>danijelzi</dc:author>
<dc:subject>intel core i7 860, lynnfield, lga1156, processor, motherboard, p55</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://computermonger.com/intel-core-i7-860.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/08/3df57bf574b856eef219d1fdbe448070.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://computermonger.com/intel-core-i7-860.html">Intel Core i7 860 CPU Now Available</a></h4>
 
by <a href="http://blogmarks.net/user/danijelzi">danijelzi</a> 
<p class="description">The Intel Core i7 860, the company’s new 45nm quad core processor, can be ordered now at Newegg. The Core i7 860 “Lynnfield” Socket LGA1156 chip is clocked at 2.8GHz. It has 8MB of cache and a TDP of 95W. The i7 860, retail model BX80605I7860, is priced at $299.99 with free shipping.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/intel%2Bcore%2Bi7%2B860">intel core i7 860</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lynnfield">lynnfield</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lga1156">lga1156</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/processor">processor</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/motherboard">motherboard</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/p55">p55</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058496976">Copy</a> | 
<a href="http://blogmarks.net/link/3337567">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/danijelzi/mark/1058496064">
<title>Intel Core i5-750 Available for Pre-Order, Coming September 8</title>
<link>http://computermonger.com/intel-core-i5-750.html</link>
<description>The Intel Core i5-750, the company’s new 45nm quad core processor, can be pre-ordered now and will be available on September 8, according to a product page at SuperBiiz.com. The first Core i5 CPU is clocked at 2.66GHz. It has 8MB of cache and a TDP of 95W. The chip is designed for the Socket LGA1156, found on new and already available Intel P55 chipset-based motherboards. The Core i5-750 is priced at $219.99, while the P55 mainboards start at $109.99.</description>
<dc:date>2009-09-07T16:49:55Z</dc:date>
<dc:author>danijelzi</dc:author>
<dc:subject>intel, Core i5-750, p55, processor, CPU, quad core, intel core</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://computermonger.com/intel-core-i5-750.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/07/1e8a3621d6d43f8fc6235ad0c30f0691.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://computermonger.com/intel-core-i5-750.html">Intel Core i5-750 Available for Pre-Order, Coming September 8</a></h4>
 
by <a href="http://blogmarks.net/user/danijelzi">danijelzi</a> 
<p class="description">The Intel Core i5-750, the company’s new 45nm quad core processor, can be pre-ordered now and will be available on September 8, according to a product page at SuperBiiz.com. The first Core i5 CPU is clocked at 2.66GHz. It has 8MB of cache and a TDP of 95W. The chip is designed for the Socket LGA1156, found on new and already available Intel P55 chipset-based motherboards. The Core i5-750 is priced at $219.99, while the P55 mainboards start at $109.99.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/intel">intel</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Core%2Bi5-750">Core i5-750</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/p55">p55</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/processor">processor</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/CPU">CPU</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/quad%2Bcore">quad core</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/intel%2Bcore">intel core</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058496064">Copy</a> | 
<a href="http://blogmarks.net/link/3336840">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058486058">
<title>Character encoding detection for external scripts</title>
<link>http://lists.w3.org/Archives/Public/www-archive/2009Aug/att-0086/script-encoding-detection.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;This is (EF BB BF) C3 B6 3D 22 21 22 loaded into browsers under various labels. That happens to be properly formed ECMAScript code for all the encodings used. The bogus results for Opera9 can easily be reproduced in context of the testing script, but probably not individually from a clean cache; what's going on there is unknown. I also noted in running these tests that Opera claims &quot;Opera supports the entire ECMA-262 2nd and 3rd standards with no exceptions&quot; while in fact their implementation does not, the parser rejects code that follows the IdentifierStart ::  UnicodeEscapeSequence production of ECMA-262 section 7.6. Instead it implements Opera-only extensions, like comma-free arrays ala [ 1 2 3 ]. Other fun facts include: IE does not implement onload for iframes and cannot modify the innerHTML or tr elements; Firefox ignores &quot;tags&quot; when setting the innerHTML of dynamically created tr elements with no ownerElement... Oh and Opera again needs /th &quot;tags&quot; so it won't nest adjacent th elements when setting innerHTML.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-30T13:29:55Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>html, implementation, parser, testing, unicode, charset</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lists.w3.org/Archives/Public/www-archive/2009Aug/att-0086/script-encoding-detection.html"><img border="0" src="http://blogmarks.net/screenshots/2009/08/30/4f7b20c7ec9e67ca1c48ae5c6a352e37.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lists.w3.org/Archives/Public/www-archive/2009Aug/att-0086/script-encoding-detection.html">Character encoding detection for external scripts</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This is (EF BB BF) C3 B6 3D 22 21 22 loaded into browsers under various labels. That happens to be properly formed ECMAScript code for all the encodings used. The bogus results for Opera9 can easily be reproduced in context of the testing script, but probably not individually from a clean cache; what's going on there is unknown. I also noted in running these tests that Opera claims "Opera supports the entire ECMA-262 2nd and 3rd standards with no exceptions" while in fact their implementation does not, the parser rejects code that follows the IdentifierStart ::  UnicodeEscapeSequence production of ECMA-262 section 7.6. Instead it implements Opera-only extensions, like comma-free arrays ala [ 1 2 3 ]. Other fun facts include: IE does not implement onload for iframes and cannot modify the innerHTML or tr elements; Firefox ignores "tags" when setting the innerHTML of dynamically created tr elements with no ownerElement... Oh and Opera again needs /th "tags" so it won't nest adjacent th elements when setting innerHTML.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/html">html</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/implementation">implementation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/parser">parser</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/testing">testing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unicode">unicode</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/charset">charset</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058486058">Copy</a> | 
<a href="http://blogmarks.net/link/3328424">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Neewok/mark/1058484626">
<title>Torrage - Torrent Storage Cache</title>
<link>http://torrage.com/</link>
<description>&lt;blockquote&gt;&lt;p&gt;You can not search or list torrent files that are stored here, you can only access them if you already know the info_hash value of the torrent you want to download.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-28T22:41:48Z</dc:date>
<dc:author>Neewok</dc:author>
<dc:subject>bittorrent</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://torrage.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/28/ae793c45744b10352d186661d2d7360e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://torrage.com/">Torrage - Torrent Storage Cache</a></h4>
 
by <a href="http://blogmarks.net/user/Neewok">Neewok</a> 
<div class="description"><blockquote><p>You can not search or list torrent files that are stored here, you can only access them if you already know the info_hash value of the torrent you want to download.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bittorrent">bittorrent</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058484626">Copy</a> | 
<a href="http://blogmarks.net/link/3327240">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/nicolargo/mark/1058484162">
<title>memcached: a distributed memory object caching system</title>
<link>http://www.danga.com/memcached/</link>
<description>MemCached: un cache libre pour vos bases de données. Un truc à suivre de très prés...</description>
<dc:date>2009-08-28T11:56:38Z</dc:date>
<dc:author>nicolargo</dc:author>
<dc:subject>cache applicatif, memcached, db</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.danga.com/memcached/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/28/a4b548d6ec34d615966b94ad7df60885.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.danga.com/memcached/">memcached: a distributed memory object caching system</a></h4>
 
by <a href="http://blogmarks.net/user/nicolargo">nicolargo</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/2243">11 other(s)</a> 
<p class="description">MemCached: un cache libre pour vos bases de données. Un truc à suivre de très prés...</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache%2Bapplicatif">cache applicatif</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memcached">memcached</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/db">db</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058484162">Copy</a> | 
<a href="http://blogmarks.net/link/2243">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mozkart/mark/1058481895">
<title>Scrnshots.com Plugin For Wordpress » Matt Varone // Matt Varone</title>
<link>http://www.mattvarone.com/wordpress/scrnshots-plugin-for-wordpress/</link>
<description>This plugin for WordPress allows you to show Scrnshots.com captures on your sites. It’s based on the great flicrkRSS plugin by Dave Kellam and is very easy to setup and configure via an admin panel. The plugin also has cache support, allowing you to save thumbnails on your own server</description>
<dc:date>2009-08-26T09:41:30Z</dc:date>
<dc:author>mozkart</dc:author>
<dc:subject>wordpress</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.mattvarone.com/wordpress/scrnshots-plugin-for-wordpress/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/26/a73d21b18c50ae9534f012b092b066c0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.mattvarone.com/wordpress/scrnshots-plugin-for-wordpress/">Scrnshots.com Plugin For Wordpress » Matt Varone // Matt Varone</a></h4>
 
by <a href="http://blogmarks.net/user/mozkart">mozkart</a> 
<p class="description">This plugin for WordPress allows you to show Scrnshots.com captures on your sites. It’s based on the great flicrkRSS plugin by Dave Kellam and is very easy to setup and configure via an admin panel. The plugin also has cache support, allowing you to save thumbnails on your own server</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpress">wordpress</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058481895">Copy</a> | 
<a href="http://blogmarks.net/link/3324985">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/paulantoinem/mark/1058488623">
<title>Qui se cache derrière les enseignes discount - Journal du Net</title>
<link>http://envrac.posterous.com/qui-se-cache-derriere-les-enseignes-discount</link>
<description>via journaldunet.com      ...</description>
<dc:date>2009-08-25T13:07:06Z</dc:date>
<dc:author>paulantoinem</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://envrac.posterous.com/qui-se-cache-derriere-les-enseignes-discount"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://envrac.posterous.com/qui-se-cache-derriere-les-enseignes-discount">Qui se cache derrière les enseignes discount - Journal du Net</a></h4>
 
by <a href="http://blogmarks.net/user/paulantoinem">paulantoinem</a> 
<p class="description">via journaldunet.com      ...</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058488623">Copy</a> | 
<a href="http://blogmarks.net/link/3330560">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058462528">
<title>DryDrop</title>
<link>http://drydrop.binaryage.com/</link>
<description>&lt;blockquote&gt;&lt;p&gt;It is simple. Let's say you have GitHub repo containing static web site and you want to host it on App Engine. DryDrop is an application ready to be uploaded as your App Engine project. When you upload it first time, you should setup post-receive hook in your GitHub repo to point to your App Engine project, so every change you push to GitHub can be reflected on your App Engine site immediately.&lt;/p&gt;&lt;p&gt;Let's say someone visits your App Engine site. DryDrop has a simple cache. If requested page is not in the cache, DryDrop will try to fetch it from GitHub, store it in the cache and then serve it. Next time the same URL is requested, it will be served directly from DryDrop cache.&lt;/p&gt;&lt;p&gt;Let's say you did some changes to your files. In the moment you push file changes into GitHub, post-receive hook will ping DryDrop and that invalidates modified files in the cache. Next request will trigger downloading of fresh files from GitHub.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-11T10:40:17Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>googleappengine, CloudComputing</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://drydrop.binaryage.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/08/11/08f6210567f1930876c887c450006b36.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://drydrop.binaryage.com/">DryDrop</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>It is simple. Let's say you have GitHub repo containing static web site and you want to host it on App Engine. DryDrop is an application ready to be uploaded as your App Engine project. When you upload it first time, you should setup post-receive hook in your GitHub repo to point to your App Engine project, so every change you push to GitHub can be reflected on your App Engine site immediately.</p><p>Let's say someone visits your App Engine site. DryDrop has a simple cache. If requested page is not in the cache, DryDrop will try to fetch it from GitHub, store it in the cache and then serve it. Next time the same URL is requested, it will be served directly from DryDrop cache.</p><p>Let's say you did some changes to your files. In the moment you push file changes into GitHub, post-receive hook will ping DryDrop and that invalidates modified files in the cache. Next request will trigger downloading of fresh files from GitHub.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/googleappengine">googleappengine</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/CloudComputing">CloudComputing</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058462528">Copy</a> | 
<a href="http://blogmarks.net/link/3312498">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058461266">
<title>Blocking Unwanted Parasites with a Hosts File</title>
<link>http://www.mvps.org/winhelp2002/hosts.htm</link>
<description>&lt;blockquote&gt;&lt;p&gt;The Hosts file contains the mappings of IP addresses to host names. This file is loaded into memory (cache) at startup, then Windows checks the Hosts file before it queries any DNS servers, which enables it to override addresses in the DNS.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-08-10T10:47:14Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>unix, spam</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.mvps.org/winhelp2002/hosts.htm"><img border="0" src="http://blogmarks.net/screenshots/2009/08/10/7517e6af0ba622582f9a56e41487adc8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.mvps.org/winhelp2002/hosts.htm">Blocking Unwanted Parasites with a Hosts File</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/242043">6 other(s)</a> 
<div class="description"><blockquote><p>The Hosts file contains the mappings of IP addresses to host names. This file is loaded into memory (cache) at startup, then Windows checks the Hosts file before it queries any DNS servers, which enables it to override addresses in the DNS.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unix">unix</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/spam">spam</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058461266">Copy</a> | 
<a href="http://blogmarks.net/link/242043">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547923">
<title>Joomla ! - CMS - Logiciels Libres - Framasoft</title>
<link>http://www.framasoft.net/article4174.html</link>
<description>Points forts :      * Mise en oeuvre quasi-immédiate ;     * Administration en français disponible ;     * Personnalisation de l’aspect (template) et du contenu de la page d’accueil très simple ;     * Gestion de la date de publication ou de fin de publication des articles ;     * Édition des balises META (titre et mots clefs) pour chaque article ;     * Gestionnaire de fichiers multimédia intégré ;     * Système de cache (Réduit les accès serveur et donc fluidifie le trafic des visites) ;     * Interface ergonomique améliorée par rapport à Joomla ! 1.0 ;     * Communauté internationale très réactive, communauté francophone importante ;     * Nombreuses extensions (forum, livre d’or, agenda, galerie...)</description>
<dc:date>2009-07-30T10:14:52Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>cms, php, site, freeware, framasoft, webdesign, dev, opensource</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.framasoft.net/article4174.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.framasoft.net/article4174.html">Joomla ! - CMS - Logiciels Libres - Framasoft</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/240953">1 other(s)</a> 
<p class="description">Points forts :      * Mise en oeuvre quasi-immédiate ;     * Administration en français disponible ;     * Personnalisation de l’aspect (template) et du contenu de la page d’accueil très simple ;     * Gestion de la date de publication ou de fin de publication des articles ;     * Édition des balises META (titre et mots clefs) pour chaque article ;     * Gestionnaire de fichiers multimédia intégré ;     * Système de cache (Réduit les accès serveur et donc fluidifie le trafic des visites) ;     * Interface ergonomique améliorée par rapport à Joomla ! 1.0 ;     * Communauté internationale très réactive, communauté francophone importante ;     * Nombreuses extensions (forum, livre d’or, agenda, galerie...)</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cms">cms</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/site">site</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/freeware">freeware</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/framasoft">framasoft</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesign">webdesign</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dev">dev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opensource">opensource</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547923">Copy</a> | 
<a href="http://blogmarks.net/link/240953">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058547924">
<title>Mambo - CMS - Logiciels Libres - Framasoft</title>
<link>http://www.framasoft.net/article2166.html</link>
<description>Points forts :      * mise en oeuvre quasi immédiate ;     * personnalisation de l’aspect et du contenu de la page d’accueil très simple ;     * système de cache (permet de moins solliciter le serveur et donc de fluidifier le trafic induit par les visites) ;     * interface ergonomique ;     * communauté très réactive ;     * nombreux composants et modules (forum, livre d’or, agenda...) ;     * version pré-modée française sur Mambofrance.org.</description>
<dc:date>2009-07-30T10:12:12Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>cms, opensource, webdesign, site, freeware, framasoft</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.framasoft.net/article2166.html"><img border="0" src="http://blogmarks.net/screenshots/2006/08/06/a638d3f2f0eeadb735bb7cc891ce28f4.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.framasoft.net/article2166.html">Mambo - CMS - Logiciels Libres - Framasoft</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/83983">1 other(s)</a> 
<p class="description">Points forts :      * mise en oeuvre quasi immédiate ;     * personnalisation de l’aspect et du contenu de la page d’accueil très simple ;     * système de cache (permet de moins solliciter le serveur et donc de fluidifier le trafic induit par les visites) ;     * interface ergonomique ;     * communauté très réactive ;     * nombreux composants et modules (forum, livre d’or, agenda...) ;     * version pré-modée française sur Mambofrance.org.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cms">cms</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opensource">opensource</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webdesign">webdesign</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/site">site</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/freeware">freeware</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/framasoft">framasoft</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058547924">Copy</a> | 
<a href="http://blogmarks.net/link/83983">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kruty/mark/1058427027">
<title>Encore sur le cache de l’iPhone — Performance web</title>
<link>http://performance.survol.fr/2008/12/encore-sur-le-cache-de-liphone/</link>
<description></description>
<dc:date>2009-07-13T16:21:21Z</dc:date>
<dc:author>kruty</dc:author>
<dc:subject>web</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://performance.survol.fr/2008/12/encore-sur-le-cache-de-liphone/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/13/a5831f825bfc77928c4899f3684ce161.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://performance.survol.fr/2008/12/encore-sur-le-cache-de-liphone/">Encore sur le cache de l’iPhone — Performance web</a></h4>
 
by <a href="http://blogmarks.net/user/kruty">kruty</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web">web</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058427027">Copy</a> | 
<a href="http://blogmarks.net/link/3284473">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kruty/mark/1058427026">
<title>Cache Safari de l’iPhone: pas très éfficace … | Webd</title>
<link>http://webd.fr/164-cache-safari-iphone-pas-tres-performant</link>
<description>    Encore il y a peu nous parlions d’un cache HTTP limité à 25ko par composant sur l’iPhone, 500ko au total. On parle de la taille une fois la ressource décompressée (sans gzip donc). 25ko c’est peu, la plupart des sites ont un composant qui dépasse cette taille. 500ko ce n’est pas beaucoup mieux, naviguez sur un ou deux sites et le cache aura complètement oublié vos précédentes visites. Pire, des bibliothèques javascript comme jquery dépassent les 25ko et donc ne passeront jamais dans le cache.

    La bonne nouvelle c’est que cette limite est désormais dépassée. Une présentation de Nicole Sullivan indique que la limite des 25ko a disparue, et que la taille globale du cache a été doublée. 

</description>
<dc:date>2009-07-13T16:20:56Z</dc:date>
<dc:author>kruty</dc:author>
<dc:subject></dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://webd.fr/164-cache-safari-iphone-pas-tres-performant"><img border="0" src="http://blogmarks.net/screenshots/2009/07/13/28bbac0601c5981b8eadb8f7bfca324d.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://webd.fr/164-cache-safari-iphone-pas-tres-performant">Cache Safari de l’iPhone: pas très éfficace … | Webd</a></h4>
 
by <a href="http://blogmarks.net/user/kruty">kruty</a> 
<p class="description">    Encore il y a peu nous parlions d’un cache HTTP limité à 25ko par composant sur l’iPhone, 500ko au total. On parle de la taille une fois la ressource décompressée (sans gzip donc). 25ko c’est peu, la plupart des sites ont un composant qui dépasse cette taille. 500ko ce n’est pas beaucoup mieux, naviguez sur un ou deux sites et le cache aura complètement oublié vos précédentes visites. Pire, des bibliothèques javascript comme jquery dépassent les 25ko et donc ne passeront jamais dans le cache.

    La bonne nouvelle c’est que cette limite est désormais dépassée. Une présentation de Nicole Sullivan indique que la limite des 25ko a disparue, et que la taille globale du cache a été doublée. 

</p>
<p class="tags">
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058427026">Copy</a> | 
<a href="http://blogmarks.net/link/3284471">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kasi77/mark/1058417147">
<title>Facebook | Articles de Engineering @ Facebook</title>
<link>http://www.facebook.com/note.php?note_id=96390263919</link>
<description>One terabyte of in-memory cache was dedicated exclusively for the username launch.
</description>
<dc:date>2009-07-05T17:15:17Z</dc:date>
<dc:author>kasi77</dc:author>
<dc:subject>facebook, memcached</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.facebook.com/note.php?note_id=96390263919"><img border="0" src="http://blogmarks.net/screenshots/2009/07/05/8066323e02c83f53e266145987eab81c.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.facebook.com/note.php?note_id=96390263919">Facebook | Articles de Engineering @ Facebook</a></h4>
 
by <a href="http://blogmarks.net/user/kasi77">kasi77</a> 
<p class="description">One terabyte of in-memory cache was dedicated exclusively for the username launch.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/facebook">facebook</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=1058417147">Copy</a> | 
<a href="http://blogmarks.net/link/3276388">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/tisienpo/mark/1058345645">
<title>adverbrain » Un Social Game pour Twitter, Spymaster - le cerveau du marketing sur Internet</title>
<link>http://www.adverbrain.com/1321-un-social-game-pour-twitter-spymaster</link>
<description>Pour les joueurs

Depuis quelques jours, je reçois des Direct Messages qui m’invitent à devenir espion sur le jeu Spymaster. Sur le même principe que les messages de blip.fm, qui ennuient surement plus d’un twitteux, j’ai malgré tout été attiré par l’air de défi du twitt.  J’ai donc franchit le cap pour découvrir ce qui se cache derrière le jeu. Même si tout est en anglais, mon initiation à Spymaster c’est faite sans douleur. Spymaster s’avère être un jeu de stratégie simplifié à vocation social (twitter oblige) du type Vampire ou Mafia sur Facebook.

Le but du jeu est d’amasser un maximum de monnaie, monter en niveau (comme tout RPG) et acquérir les meilleures armes, tout cela  pour affirmer son pouvoir auprès de tous les autres twitteux de son réseau ou non.

Au programme des actions on pourra assassiner, acheter des armes et protections au marché noir, déposer des sous sur son compte en suisse, prendre possession de bâtiments qui rapportent (comme dans le Parrain 2 sur ps3), inviter les twitteux de son réseau à jouer ou encore spammer complètement les timelines de nos amis si on ne configure pas bien notre compte.

Résultat il est complet et promet de belles heures de jeu aux assidus. Néanmoins je redoute le spam qui peut se dégager de ce type de jeu. Même si l’accent est mis sur les Directs messages plutôt que la timeline, les invitations risque fort d’en énerver plus d’un, d’autant plus qu’il n’est pas possible de personnaliser le message.

image-7

Pour les marketeurs

Nous avons ici un exemple typique de social game, mélange de casual game et de réseau social. Ce type de jeu nous invite à interagir avec notre réseau pour avancer dans le jeu ou simplement pour pouvoir y jouer. Il est indissociable d’un réseau social. L’intérêt est qu’il existe en amont de ces jeux une large audience. De plus, l’utilisation d’une plateforme social (twitter, facebook, etc…) permet aux socials games et notamment à Spymaster, de profiter des outils de communication qui augmentent considérablement l’intérêt du jeu. La viralité de ce dernier est de la même manière, décuplée.

Le business modèle du jeu n’est pas encore apparent mais on peut dire que les développeurs ont le choix de l’angle d’attaque. Entre les abonnements, les micro-transactions (achat par allopass de capacités spéciales pour avancer dans le jeu), la publicité ou le sponsoring, le social game peut être considéré comme une véritable mine d’or .

Pour un annonceur l’intérêt est de pouvoir approcher soit une catégorie de personne ciblée via une expérience ludique sur un réseau de niche, soit approcher une large catégorie de personnes amatrices de casual gaming sur un réseau plus large (ex : twitter). La viralité de l’application et sa simplicité de diffusion (via les outils de la plateforme social) permettent de multiplier l’impact sur les réseaux et ainsi diffuser efficacement un message. Pour le joueur l’intérêt est décuplé dans la mesure où il peut partager cette expérience avec ses amis.

Une expérience du type avec twitter avait déjà été faites avec le site twoof. On y redoutait déjà le spam sur twitter et j’avais pu remarquer que le site n’était pas énormément fréquenté. Alors peut-on dire que les twitteux sont des gamers ou des spammeurs ?</description>
<dc:date>2009-06-02T16:43:53Z</dc:date>
<dc:author>tisienpo</dc:author>
<dc:subject>marketing, spymaster, twitter, social gaming</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.adverbrain.com/1321-un-social-game-pour-twitter-spymaster"><img border="0" src="http://blogmarks.net/screenshots/2009/08/10/24b9e91eff94cdc354ac5dd1371a2c97.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.adverbrain.com/1321-un-social-game-pour-twitter-spymaster">adverbrain » Un Social Game pour Twitter, Spymaster - le cerveau du marketing sur Internet</a></h4>
 
by <a href="http://blogmarks.net/user/tisienpo">tisienpo</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3215184">1 other(s)</a> 
<p class="description">Pour les joueurs

Depuis quelques jours, je reçois des Direct Messages qui m’invitent à devenir espion sur le jeu Spymaster. Sur le même principe que les messages de blip.fm, qui ennuient surement plus d’un twitteux, j’ai malgré tout été attiré par l’air de défi du twitt.  J’ai donc franchit le cap pour découvrir ce qui se cache derrière le jeu. Même si tout est en anglais, mon initiation à Spymaster c’est faite sans douleur. Spymaster s’avère être un jeu de stratégie simplifié à vocation social (twitter oblige) du type Vampire ou Mafia sur Facebook.

Le but du jeu est d’amasser un maximum de monnaie, monter en niveau (comme tout RPG) et acquérir les meilleures armes, tout cela  pour affirmer son pouvoir auprès de tous les autres twitteux de son réseau ou non.

Au programme des actions on pourra assassiner, acheter des armes et protections au marché noir, déposer des sous sur son compte en suisse, prendre possession de bâtiments qui rapportent (comme dans le Parrain 2 sur ps3), inviter les twitteux de son réseau à jouer ou encore spammer complètement les timelines de nos amis si on ne configure pas bien notre compte.

Résultat il est complet et promet de belles heures de jeu aux assidus. Néanmoins je redoute le spam qui peut se dégager de ce type de jeu. Même si l’accent est mis sur les Directs messages plutôt que la timeline, les invitations risque fort d’en énerver plus d’un, d’autant plus qu’il n’est pas possible de personnaliser le message.

image-7

Pour les marketeurs

Nous avons ici un exemple typique de social game, mélange de casual game et de réseau social. Ce type de jeu nous invite à interagir avec notre réseau pour avancer dans le jeu ou simplement pour pouvoir y jouer. Il est indissociable d’un réseau social. L’intérêt est qu’il existe en amont de ces jeux une large audience. De plus, l’utilisation d’une plateforme social (twitter, facebook, etc…) permet aux socials games et notamment à Spymaster, de profiter des outils de communication qui augmentent considérablement l’intérêt du jeu. La viralité de ce dernier est de la même manière, décuplée.

Le business modèle du jeu n’est pas encore apparent mais on peut dire que les développeurs ont le choix de l’angle d’attaque. Entre les abonnements, les micro-transactions (achat par allopass de capacités spéciales pour avancer dans le jeu), la publicité ou le sponsoring, le social game peut être considéré comme une véritable mine d’or .

Pour un annonceur l’intérêt est de pouvoir approcher soit une catégorie de personne ciblée via une expérience ludique sur un réseau de niche, soit approcher une large catégorie de personnes amatrices de casual gaming sur un réseau plus large (ex : twitter). La viralité de l’application et sa simplicité de diffusion (via les outils de la plateforme social) permettent de multiplier l’impact sur les réseaux et ainsi diffuser efficacement un message. Pour le joueur l’intérêt est décuplé dans la mesure où il peut partager cette expérience avec ses amis.

Une expérience du type avec twitter avait déjà été faites avec le site twoof. On y redoutait déjà le spam sur twitter et j’avais pu remarquer que le site n’était pas énormément fréquenté. Alors peut-on dire que les twitteux sont des gamers ou des spammeurs ?</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/marketing">marketing</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/spymaster">spymaster</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/twitter">twitter</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/social%2Bgaming">social gaming</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058345645">Copy</a> | 
<a href="http://blogmarks.net/link/3215184">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/mozkart/mark/1058338914">
<title>WP Greet Box WordPress Plugin | OMNINOGGIN</title>
<link>http://omninoggin.com/projects/wordpress-plugins/wp-greet-box-wordpress-plugin/</link>
<description>This plugin lets you show a different greeting message to your new visitors depending on their referrer url. For example, when a Digg user clicks through from Digg, they will see a message reminding them to digg your post if they like it. Another example, when a visitor clicks through from Twitter, they will see a message suggesting them to twit the post and follow you on Twitter. You can also set a default greeting message for new visitors (not matching any referrer URLs) suggesting them to subscribe to your RSS feed. Professional bloggers know that having these targeted suggestions on their blog increases their blog exposure and loyal readership. Best of all, this plugin is compatible with various WordPress cache plugins so you do not have to sacrifice speed.  Even Smashing Magazine is using this plugin.  Take it from the pros and download it!</description>
<dc:date>2009-05-28T02:26:31Z</dc:date>
<dc:author>mozkart</dc:author>
<dc:subject>wordpress</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://omninoggin.com/projects/wordpress-plugins/wp-greet-box-wordpress-plugin/"><img border="0" src="http://blogmarks.net/screenshots/2009/05/28/2b3ad338f8084abd61cc5d75307399b0.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://omninoggin.com/projects/wordpress-plugins/wp-greet-box-wordpress-plugin/">WP Greet Box WordPress Plugin | OMNINOGGIN</a></h4>
 
by <a href="http://blogmarks.net/user/mozkart">mozkart</a> 
<p class="description">This plugin lets you show a different greeting message to your new visitors depending on their referrer url. For example, when a Digg user clicks through from Digg, they will see a message reminding them to digg your post if they like it. Another example, when a visitor clicks through from Twitter, they will see a message suggesting them to twit the post and follow you on Twitter. You can also set a default greeting message for new visitors (not matching any referrer URLs) suggesting them to subscribe to your RSS feed. Professional bloggers know that having these targeted suggestions on their blog increases their blog exposure and loyal readership. Best of all, this plugin is compatible with various WordPress cache plugins so you do not have to sacrifice speed.  Even Smashing Magazine is using this plugin.  Take it from the pros and download it!</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/wordpress">wordpress</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058338914">Copy</a> | 
<a href="http://blogmarks.net/link/3209407">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>