<?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/avoided">
<title>Public marks with search avoided</title>
<description>Public marks with search avoided</description>
<link>http://blogmarks.net/marks/search/avoided</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058327645"/>
<rdf:li resource="http://blogmarks.net/api/user/polyxena/mark/1058212181"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1057984417"/>
<rdf:li resource="http://blogmarks.net/api/user/marco/mark/1057829513"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1057265094"/>
<rdf:li resource="http://blogmarks.net/api/user/znarf/mark/2669911"/>
<rdf:li resource="http://blogmarks.net/api/user/cyberien/mark/2589521"/>
<rdf:li resource="http://blogmarks.net/api/user/camel/mark/2435248"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1354973"/>
<rdf:li resource="http://blogmarks.net/api/user/springnet/mark/1057902289"/>
<rdf:li resource="http://blogmarks.net/api/user/kmlawson/mark/537429"/>
<rdf:li resource="http://blogmarks.net/api/user/music2084/mark/460007"/>
<rdf:li resource="http://blogmarks.net/api/user/bcpbcp/mark/177376"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/230166"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058327645">
<title>Five reasons why the shut-op operator (@) should be avoided - Derick Rethans</title>
<link>http://derickrethans.nl/five_reasons_why_the_shutop_operator_@_should_be_avoided.php</link>
<description></description>
<dc:date>2009-05-17T17:05:29Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>php, gesttion des erreurs</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://derickrethans.nl/five_reasons_why_the_shutop_operator_@_should_be_avoided.php"><img border="0" src="http://blogmarks.net/screenshots/2009/05/17/6224d1f92f83520d8e5bc22203774cc7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://derickrethans.nl/five_reasons_why_the_shutop_operator_@_should_be_avoided.php">Five reasons why the shut-op operator (@) should be avoided - Derick Rethans</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/php">php</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gesttion%2Bdes%2Berreurs">gesttion des erreurs</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058327645">Copy</a> | 
<a href="http://blogmarks.net/link/3199544">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/polyxena/mark/1058212181">
<title>Contract for Difference Trading - CFD</title>
<link>http://www.forexperform.com/2009/02/17/contract-for-difference-trading-cfd/</link>
<description>CFDs are to be avoided, on stocks, equities, anything and everything - it’s one small step away from spread betting and if you want to end up like those dumbasses who spreadbet on the FTSE opening every morning, fine, go ahead…</description>
<dc:date>2009-02-17T14:22:33Z</dc:date>
<dc:author>polyxena</dc:author>
<dc:subject>forex, finance, markets, money</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.forexperform.com/2009/02/17/contract-for-difference-trading-cfd/"><img border="0" src="http://blogmarks.net/screenshots/2009/02/17/933c010460e7a92785d6da92b3dcd305.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.forexperform.com/2009/02/17/contract-for-difference-trading-cfd/">Contract for Difference Trading - CFD</a></h4>
 
by <a href="http://blogmarks.net/user/polyxena">polyxena</a> 
<p class="description">CFDs are to be avoided, on stocks, equities, anything and everything - it’s one small step away from spread betting and if you want to end up like those dumbasses who spreadbet on the FTSE opening every morning, fine, go ahead…</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/forex">forex</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/finance">finance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/markets">markets</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/money">money</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058212181">Copy</a> | 
<a href="http://blogmarks.net/link/3102389">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1057984417">
<title>Dorothea Salo's Keynote, Repository Fringe 2008</title>
<link>http://video.google.co.uk/videoplay?docid=8823043830385196768&amp;ei=546-SOi_HYTgjAKZnuiTCQ&amp;q=repository fringe&amp;hl=en</link>
<description>Le IR, c'est mort. Vive le IR! The institutional repository is dead -- long live the institutional repository! Despite their rocky beginnings, IRs are finally finding their niche and surging forward. What were their initial mistakes, and how can further missteps be avoided? How do we best build on IRs' current momentum? What do IRs need to succeed? Let's get the conversation started!</description>
<dc:date>2008-09-16T08:26:45Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>dspace, institutional repository</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://video.google.co.uk/videoplay?docid=8823043830385196768&amp;ei=546-SOi_HYTgjAKZnuiTCQ&amp;q=repository fringe&amp;hl=en"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://video.google.co.uk/videoplay?docid=8823043830385196768&amp;ei=546-SOi_HYTgjAKZnuiTCQ&amp;q=repository fringe&amp;hl=en">Dorothea Salo's Keynote, Repository Fringe 2008</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">Le IR, c'est mort. Vive le IR! The institutional repository is dead -- long live the institutional repository! Despite their rocky beginnings, IRs are finally finding their niche and surging forward. What were their initial mistakes, and how can further missteps be avoided? How do we best build on IRs' current momentum? What do IRs need to succeed? Let's get the conversation started!</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/dspace">dspace</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/institutional%2Brepository">institutional repository</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057984417">Copy</a> | 
<a href="http://blogmarks.net/link/2900464">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/marco/mark/1057829513">
<title>line-height: abnormal</title>
<link>http://meyerweb.com/eric/thoughts/2008/05/06/line-height-abnormal/</link>
<description>line-height: normal is a jumbled terrain of inconsistent behaviors, and it's best avoided in any sort of precision layout work</description>
<dc:date>2008-05-06T20:17:36Z</dc:date>
<dc:author>marco</dc:author>
<dc:subject>layout, css, line-height, font</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://meyerweb.com/eric/thoughts/2008/05/06/line-height-abnormal/"><img border="0" src="http://blogmarks.net/screenshots/2008/05/06/33c559274bfd5d4a57936a1b1b0925f9.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://meyerweb.com/eric/thoughts/2008/05/06/line-height-abnormal/">line-height: abnormal</a></h4>
 
by <a href="http://blogmarks.net/user/marco">marco</a> 
<p class="description">line-height: normal is a jumbled terrain of inconsistent behaviors, and it's best avoided in any sort of precision layout work</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/layout">layout</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/line-height">line-height</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/font">font</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057829513">Copy</a> | 
<a href="http://blogmarks.net/link/2770603">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1057265094">
<title>A Race to the Bottom - Privacy Ranking of Internet Service Companies</title>
<link>http://www.privacyinternational.org/article.shtml?cmd[347]=x-347-553961</link>
<description>Why not Microsoft?

The finding that Microsoft is a better privacy performer than Google is also likely to be contentious. Microsoft was awarded &quot;orange&quot; status, two bands better than Google's position. However it is important, for the sake of clarity, to note that Windows Live Space received the more negative &quot;red&quot; rating, while Google's Orkut avoided a black rating and was awarded red status.</description>
<dc:date>2007-06-11T06:46:50Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>vieprivee, google</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.privacyinternational.org/article.shtml?cmd[347]=x-347-553961"><img border="0" src="http://blogmarks.net/screenshots/2007/06/11/8971c66d9d1f8f2802623f04d154252b.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.privacyinternational.org/article.shtml?cmd[347]=x-347-553961">A Race to the Bottom - Privacy Ranking of Internet Service Companies</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<p class="description">Why not Microsoft?

The finding that Microsoft is a better privacy performer than Google is also likely to be contentious. Microsoft was awarded "orange" status, two bands better than Google's position. However it is important, for the sake of clarity, to note that Windows Live Space received the more negative "red" rating, while Google's Orkut avoided a black rating and was awarded red status.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/vieprivee">vieprivee</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057265094">Copy</a> | 
<a href="http://blogmarks.net/link/2286337">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/znarf/mark/2669911">
<title>How Digg could have avoided a community revolt at Demand Satisfaction!</title>
<link>http://blog.getsatisfaction.com/2007/05/03/how-digg-could-have-avoided-a-community-revolt/</link>
<description></description>
<dc:date>2007-05-03T20:15:17Z</dc:date>
<dc:author>François Hodierne</dc:author>
<dc:subject>digg</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://blog.getsatisfaction.com/2007/05/03/how-digg-could-have-avoided-a-community-revolt/"><img border="0" src="http://blogmarks.net/screenshots/2007/05/03/9d1732d7c42fc4ebcaa29190d1c7ec09.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://blog.getsatisfaction.com/2007/05/03/how-digg-could-have-avoided-a-community-revolt/">How Digg could have avoided a community revolt at Demand Satisfaction!</a></h4>
 
by <a href="http://blogmarks.net/user/znarf">François Hodierne</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/digg">digg</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2669911">Copy</a> | 
<a href="http://blogmarks.net/link/2195288">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/cyberien/mark/2589521">
<title>Gigya</title>
<link>http://www.gigya.com/web/info/partners.aspx</link>
<description>wildfire post lets users post your content to their own pages on their community site or blog, without leaving your site. 
We found out that users post more when the hassle of copying and pasting code is avoided. And again, it helps you keep your users within your site.</description>
<dc:date>2007-04-18T04:21:50Z</dc:date>
<dc:author>cyberien</dc:author>
<dc:subject>widget</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.gigya.com/web/info/partners.aspx"><img border="0" src="http://blogmarks.net/screenshots/2007/04/18/726560ee6415bb10cc2fd6c051753aac.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.gigya.com/web/info/partners.aspx">Gigya</a></h4>
 
by <a href="http://blogmarks.net/user/cyberien">cyberien</a> 
<p class="description">wildfire post lets users post your content to their own pages on their community site or blog, without leaving your site. 
We found out that users post more when the hassle of copying and pasting code is avoided. And again, it helps you keep your users within your site.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/widget">widget</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2589521">Copy</a> | 
<a href="http://blogmarks.net/link/2120311">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/camel/mark/2435248">
<title>CSS Hacks</title>
<link>http://www.webdevout.net/articles/css_hacks.php#p2006.4.28.22.56:12</link>
<description>
      Dealing with browser inconsistencies often makes up a majority of the work for a web designer. Sometimes there is no reasonable way to accomplish a desired layout in all major web browsers without the use of some special exception rules for certain layout engines. Hacks necessarily lead to potential complications and should be avoided whenever possible, but when the circumstances require hacks to be used, it's best to know what your options are and weigh the consequences appropriately. The purpose of this article is to describe some of the CSS hacks, also called CSS filters, with the least significant potential consequences.
    </description>
<dc:date>2006-12-11T08:59:54Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>css, hack</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.webdevout.net/articles/css_hacks.php#p2006.4.28.22.56:12"><img border="0" src="http://blogmarks.net/screenshots/2006/12/11/1d11bef1d3cc4ecc127d2cfefc28a3e8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.webdevout.net/articles/css_hacks.php#p2006.4.28.22.56:12">CSS Hacks</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1342998">1 other(s)</a> 
<p class="description">
      Dealing with browser inconsistencies often makes up a majority of the work for a web designer. Sometimes there is no reasonable way to accomplish a desired layout in all major web browsers without the use of some special exception rules for certain layout engines. Hacks necessarily lead to potential complications and should be avoided whenever possible, but when the circumstances require hacks to be used, it's best to know what your options are and weigh the consequences appropriately. The purpose of this article is to describe some of the CSS hacks, also called CSS filters, with the least significant potential consequences.
    </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/hack">hack</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2435248">Copy</a> | 
<a href="http://blogmarks.net/link/1342998">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1354973">
<title>CSS Hacks</title>
<link>http://www.webdevout.net/articles/css_hacks.php#p2006.4.28.22.56:12</link>
<description>Dealing with browser inconsistencies often makes up a majority of the work for a web designer. Sometimes there is no reasonable way to accomplish a desired layout in all major web browsers without the use of some special exception rules for certain layout engines. Hacks necessarily lead to potential complications and should be avoided whenever possible, but when the circumstances require hacks to be used, it's best to know what your options are and weigh the consequences appropriately. The purpose of this article is to describe some of the CSS hacks, also called CSS filters, with the least significant potential consequences.</description>
<dc:date>2006-12-11T08:34:14Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>web, dev, css</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.webdevout.net/articles/css_hacks.php#p2006.4.28.22.56:12"><img border="0" src="http://blogmarks.net/screenshots/2006/12/11/1d11bef1d3cc4ecc127d2cfefc28a3e8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.webdevout.net/articles/css_hacks.php#p2006.4.28.22.56:12">CSS Hacks</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1342998">1 other(s)</a> 
<p class="description">Dealing with browser inconsistencies often makes up a majority of the work for a web designer. Sometimes there is no reasonable way to accomplish a desired layout in all major web browsers without the use of some special exception rules for certain layout engines. Hacks necessarily lead to potential complications and should be avoided whenever possible, but when the circumstances require hacks to be used, it's best to know what your options are and weigh the consequences appropriately. The purpose of this article is to describe some of the CSS hacks, also called CSS filters, with the least significant potential consequences.</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/dev">dev</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1354973">Copy</a> | 
<a href="http://blogmarks.net/link/1342998">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/springnet/mark/1057902289">
<title>PHPBuilder.com, the best resource for PHP tutorials, templates, PHP manuals, content management systems, scripts, classes and more.</title>
<link>http://www.phpbuilder.com/</link>
<description>PHP Filtering with OWASP By Ryan McGeehan This tutorial is aimed to introduce the reader to PHP filters from OWASP, the Open Web Application Security Project. Most of the top ten vulnerabilities can be avoided by using these filters--find out if you're re</description>
<dc:date>2006-07-24T03:15:21Z</dc:date>
<dc:author>springnet</dc:author>
<dc:subject>owasp, tutorials, php, sxsw, texas, austin, austinblogger, austincast, walhus, springnet</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.phpbuilder.com/"><img border="0" src="http://blogmarks.net/screenshots/2007/02/05/25c14245f4eb8ff2f410df13975cd795.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.phpbuilder.com/">PHPBuilder.com, the best resource for PHP tutorials, templates, PHP manuals, content management systems, scripts, classes and more.</a></h4>
 
by <a href="http://blogmarks.net/user/springnet">springnet</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/44916">20 other(s)</a> 
<p class="description">PHP Filtering with OWASP By Ryan McGeehan This tutorial is aimed to introduce the reader to PHP filters from OWASP, the Open Web Application Security Project. Most of the top ten vulnerabilities can be avoided by using these filters--find out if you're re</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/owasp">owasp</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorials">tutorials</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/sxsw">sxsw</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/texas">texas</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/austin">austin</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/austinblogger">austinblogger</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/austincast">austincast</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/walhus">walhus</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/springnet">springnet</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057902289">Copy</a> | 
<a href="http://blogmarks.net/link/44916">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/kmlawson/mark/537429">
<title>Former head priest at Yasukuni Shrine avoided enshrining class-A war criminals - MSN-Mainichi Daily News</title>
<link>http://mdn.mainichi-msn.co.jp/national/news/20060429p2a00m0na036000c.html</link>
<description></description>
<dc:date>2006-05-05T05:37:04Z</dc:date>
<dc:author>kmlawson</dc:author>
<dc:subject>japan, history</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://mdn.mainichi-msn.co.jp/national/news/20060429p2a00m0na036000c.html"><img border="0" src="http://www.blogmarks.net/screenshots/2006/05/05/f450ec129d48cc9fdf4a07fc1d76a233.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://mdn.mainichi-msn.co.jp/national/news/20060429p2a00m0na036000c.html">Former head priest at Yasukuni Shrine avoided enshrining class-A war criminals - MSN-Mainichi Daily News</a></h4>
 
by <a href="http://blogmarks.net/user/kmlawson">kmlawson</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/japan">japan</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/history">history</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=537429">Copy</a> | 
<a href="http://blogmarks.net/link/829220">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/music2084/mark/460007">
<title>Mine by Gillian Middleton</title>
<link>http://www.fanfiction.net/s/1963825/1/</link>
<description>Against his better judgement Severus Snape let a part of himself be used in a spell six years earlier. Now the consequences of his actions cannot be avoided any longer and Snape finds himself the father of a five year old boy-Harry Potter! #</description>
<dc:date>2006-03-30T19:54:43Z</dc:date>
<dc:author>music2084</dc:author>
<dc:subject>g, gen, harry, harry_potter, Severus, LIKED</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.fanfiction.net/s/1963825/1/"><img border="0" src="http://www.blogmarks.net/screenshots/2006/03/30/0c4373fef52afb01d06171f063069238.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.fanfiction.net/s/1963825/1/">Mine by Gillian Middleton</a></h4>
 
by <a href="http://blogmarks.net/user/music2084">music2084</a> 
<p class="description">Against his better judgement Severus Snape let a part of himself be used in a spell six years earlier. Now the consequences of his actions cannot be avoided any longer and Snape finds himself the father of a five year old boy-Harry Potter! #</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/g">g</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gen">gen</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/harry">harry</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/harry_potter">harry_potter</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Severus">Severus</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/LIKED">LIKED</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=460007">Copy</a> | 
<a href="http://blogmarks.net/link/697981">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/bcpbcp/mark/177376">
<title>Continuations And Stackless Python</title>
<link>http://stackless.com/spcpaper.htm#_Toc470444065</link>
<description>In this paper, an implementation of &quot;Stackless Python&quot; (a Python which does not keep state on the C stack) is presented. Surprisingly, the necessary changes affect just a small number of C modules, and a major rewrite of the C library can be avoided. The key idea in this approach is a paradigm change for the Python code interpreter that is not easy to understand in the first place. Recursive interpreter calls are turned into tail recursion, which allows deferring evaluation by pushing frames to the frame stack, without the C stack involved.</description>
<dc:date>2005-10-14T18:42:01Z</dc:date>
<dc:author>bcpbcp</dc:author>
<dc:subject>python, 2005, article, library, scripting, gameai, stackless.com</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://stackless.com/spcpaper.htm#_Toc470444065"><img border="0" src="http://www.blogmarks.net/screenshots/2005/10/14/1e10906e16e087f678ed2a33f869d011.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://stackless.com/spcpaper.htm#_Toc470444065">Continuations And Stackless Python</a></h4>
 
by <a href="http://blogmarks.net/user/bcpbcp">bcpbcp</a> 
<p class="description">In this paper, an implementation of "Stackless Python" (a Python which does not keep state on the C stack) is presented. Surprisingly, the necessary changes affect just a small number of C modules, and a major rewrite of the C library can be avoided. The key idea in this approach is a paradigm change for the Python code interpreter that is not easy to understand in the first place. Recursive interpreter calls are turned into tail recursion, which allows deferring evaluation by pushing frames to the frame stack, without the C stack involved.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/python">python</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/2005">2005</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/article">article</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/scripting">scripting</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/gameai">gameai</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/stackless.com">stackless.com</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=177376">Copy</a> | 
<a href="http://blogmarks.net/link/262219">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/230166">
<title>Flangy Software: GET after POST</title>
<link>http://adamv.com/dev/articles/getafterpost</link>
<description>When handling a web form that was POSTed to a page, redirect from the POST handler to the success page. If the user reloads the success page, the &quot;page expired&quot; warning is avoided.</description>
<dc:date>2005-05-17T13:34:42Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>w3c, http, post, get</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://adamv.com/dev/articles/getafterpost"><img border="0" src="http://www.blogmarks.net/screenshots/2005/05/17/505fb55e94683b5ed902993db71eab88.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://adamv.com/dev/articles/getafterpost">Flangy Software: GET after POST</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<p class="description">When handling a web form that was POSTed to a page, redirect from the POST handler to the success page. If the user reloads the success page, the "page expired" warning is avoided.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/w3c">w3c</a>
<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/post">post</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/get">get</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=230166">Copy</a> | 
<a href="http://blogmarks.net/link/348827">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>