<?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/z-buffer">
<title>Public marks with search z-buffer</title>
<description>Public marks with search z-buffer</description>
<link>http://blogmarks.net/marks/search/z-buffer</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058593365"/>
<rdf:li resource="http://blogmarks.net/api/user/Fulcanelli/mark/1058509692"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1058159890"/>
<rdf:li resource="http://blogmarks.net/api/user/helmeloh/mark/1058055780"/>
<rdf:li resource="http://blogmarks.net/api/user/parmentierf/mark/1057987634"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1057951936"/>
<rdf:li resource="http://blogmarks.net/api/user/BlueVoodoo/mark/1057737945"/>
<rdf:li resource="http://blogmarks.net/api/user/cascamorto/mark/1057600789"/>
<rdf:li resource="http://blogmarks.net/api/user/BlueVoodoo/mark/1057402922"/>
<rdf:li resource="http://blogmarks.net/api/user/benoit/mark/1057399034"/>
<rdf:li resource="http://blogmarks.net/api/user/sylvainulg/mark/1057390784"/>
<rdf:li resource="http://blogmarks.net/api/user/wrijneveld/mark/1057669607"/>
<rdf:li resource="http://blogmarks.net/api/user/chunmin/mark/2689373"/>
<rdf:li resource="http://blogmarks.net/api/user/phumblot/mark/1910929"/>
<rdf:li resource="http://blogmarks.net/api/user/ionobelisk/mark/1878672"/>
<rdf:li resource="http://blogmarks.net/api/user/pvergain/mark/1741894"/>
<rdf:li resource="http://blogmarks.net/api/user/chachapoya/mark/1258257"/>
<rdf:li resource="http://blogmarks.net/api/user/ogrisel/mark/1135501"/>
<rdf:li resource="http://blogmarks.net/api/user/YukuanMark/mark/1146389"/>
<rdf:li resource="http://blogmarks.net/api/user/ms_michel/mark/647821"/>
<rdf:li resource="http://blogmarks.net/api/user/stan/mark/647792"/>
<rdf:li resource="http://blogmarks.net/api/user/fakechris/mark/1252850"/>
<rdf:li resource="http://blogmarks.net/api/user/taizo_onexone/mark/668345"/>
<rdf:li resource="http://blogmarks.net/api/user/jambe/mark/1976983"/>
<rdf:li resource="http://blogmarks.net/api/user/FredB/mark/1368210"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058593365">
<title>ry's http-parser at master - GitHub</title>
<link>http://github.com/ry/http-parser</link>
<description>&lt;blockquote&gt;&lt;p&gt;This is a parser for HTTP messages written in C. It parses both requests and responses. The parser is designed to be used in performance HTTP applications. It does not make any allocations, it does not buffer data, and it can be interrupted at anytime. It only requires about 128 bytes of data per message stream (in a web server that is per connection).&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-27T04:13:24Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http, parser</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://github.com/ry/http-parser"><img border="0" src="http://blogmarks.net/screenshots/2009/11/27/1c42b51e7de1f1892d28240e17f4eee8.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://github.com/ry/http-parser">ry's http-parser at master - GitHub</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>This is a parser for HTTP messages written in C. It parses both requests and responses. The parser is designed to be used in performance HTTP applications. It does not make any allocations, it does not buffer data, and it can be interrupted at anytime. It only requires about 128 bytes of data per message stream (in a web server that is per connection).</p></blockquote></div>
<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/parser">parser</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058593365">Copy</a> | 
<a href="http://blogmarks.net/link/3417203">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Fulcanelli/mark/1058509692">
<title>Initiation aux Buffer Overflow (BOF) - Remote Exploit Forums</title>
<link>http://forums.remote-exploit.org/tutoriaux-et-howtos/26709-initiation-aux-buffer-overflow-bof.html</link>
<description></description>
<dc:date>2009-09-19T16:11:20Z</dc:date>
<dc:author>Fulcanelli</dc:author>
<dc:subject>buffer, overflow</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://forums.remote-exploit.org/tutoriaux-et-howtos/26709-initiation-aux-buffer-overflow-bof.html"><img border="0" src="http://blogmarks.net/screenshots/2009/09/19/46c486630a97f9adb69dca030dede1d1.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://forums.remote-exploit.org/tutoriaux-et-howtos/26709-initiation-aux-buffer-overflow-bof.html">Initiation aux Buffer Overflow (BOF) - Remote Exploit Forums</a></h4>
 
by <a href="http://blogmarks.net/user/Fulcanelli">Fulcanelli</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/buffer">buffer</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/overflow">overflow</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058509692">Copy</a> | 
<a href="http://blogmarks.net/link/3347555">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1058159890">
<title>Safe C String Library v1.0.3 (January 30, 2005)</title>
<link>http://www.zork.org/safestr/</link>
<description>The goal of the SafeStr library is to provide a rich string-handling library for C that has safe semantics yet interoperates with legacy library code in a straightforward manner. Additionally, porting code that uses standard C string handling should be straightforward. The library should work on all modern Unix-like platforms, as well as any 32-bit Microsoft Windows OS.

The overt security goals of the library are as follows:

   1. Buffer overflows should not be possible when using the API.
   2. Format string problems should be impossible when using the API.
   3. The API should be capable of tracking whether strings are &quot;trusted&quot;, a la Perl's taint mode.

The API is meant to provide rich functionality and be easy to use, all the while improving security. </description>
<dc:date>2009-01-14T16:52:10Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>windows, standard, microsoft, c, api, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.zork.org/safestr/"><img border="0" src="http://blogmarks.net/screenshots/2009/01/14/8dc0aeb8b2e4809a3e513e44e8814fda.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.zork.org/safestr/">Safe C String Library v1.0.3 (January 30, 2005)</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">The goal of the SafeStr library is to provide a rich string-handling library for C that has safe semantics yet interoperates with legacy library code in a straightforward manner. Additionally, porting code that uses standard C string handling should be straightforward. The library should work on all modern Unix-like platforms, as well as any 32-bit Microsoft Windows OS.

The overt security goals of the library are as follows:

   1. Buffer overflows should not be possible when using the API.
   2. Format string problems should be impossible when using the API.
   3. The API should be capable of tracking whether strings are "trusted", a la Perl's taint mode.

The API is meant to provide rich functionality and be easy to use, all the while improving security. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/windows">windows</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/standard">standard</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/microsoft">microsoft</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/c">c</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/api">api</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058159890">Copy</a> | 
<a href="http://blogmarks.net/link/3057383">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/helmeloh/mark/1058055780">
<title>DSA-1654 libxml2 - buffer overflow</title>
<link>http://www.hirner.at/archives/6235</link>
<description></description>
<dc:date>2008-10-20T00:46:58Z</dc:date>
<dc:author>helmeloh</dc:author>
<dc:subject>it, security</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.hirner.at/archives/6235"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.hirner.at/archives/6235">DSA-1654 libxml2 - buffer overflow</a></h4>
 
by <a href="http://blogmarks.net/user/helmeloh">helmeloh</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/it">it</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/security">security</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058055780">Copy</a> | 
<a href="http://blogmarks.net/link/2964601">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/parmentierf/mark/1057987634">
<title>Christian Fauré — XML versus Protocol Buffer</title>
<link>http://www.christian-faure.net/2008/09/18/xml-versus-protocol-buffer/</link>
<description>C’est quoi “Protocol Buffer” ? C’est le mécanisme qu’utilise en interne Google pour sérialiser des données structurées lors d’échanges entre des systèmes ou des applicatifs.

Mais aujourd’hui on fait çà en XML non ? Exact, mais la majorité des développeurs, surtout quand il s’agit ne s’agit pas de systèmes documentaires, n’ont jamais vraiment aimé XML.</description>
<dc:date>2008-09-19T09:27:15Z</dc:date>
<dc:author>parmentierf</dc:author>
<dc:subject>xml, google, Protocol Buffer</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.christian-faure.net/2008/09/18/xml-versus-protocol-buffer/"><img border="0" src="http://blogmarks.net/screenshots/2008/09/19/567eae8e2436de69ba284568d99ef7f6.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.christian-faure.net/2008/09/18/xml-versus-protocol-buffer/">Christian Fauré — XML versus Protocol Buffer</a></h4>
 
by <a href="http://blogmarks.net/user/parmentierf">parmentierf</a> 
<p class="description">C’est quoi “Protocol Buffer” ? C’est le mécanisme qu’utilise en interne Google pour sérialiser des données structurées lors d’échanges entre des systèmes ou des applicatifs.

Mais aujourd’hui on fait çà en XML non ? Exact, mais la majorité des développeurs, surtout quand il s’agit ne s’agit pas de systèmes documentaires, n’ont jamais vraiment aimé XML.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xml">xml</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/google">google</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Protocol%2BBuffer">Protocol Buffer</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057987634">Copy</a> | 
<a href="http://blogmarks.net/link/2903571">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1057951936">
<title>Buffer overloads: the big security hole | Tech News on ZDNet</title>
<link>http://news.zdnet.com/2100-9595_22-122022.html</link>
<description>Buffer Overflow 101 for dummies.</description>
<dc:date>2008-08-18T06:59:10Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>tutorial, sécurité</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://news.zdnet.com/2100-9595_22-122022.html"><img border="0" src="http://blogmarks.net/screenshots/2008/08/18/72f077922a3570be0ffa11377f3e9df7.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://news.zdnet.com/2100-9595_22-122022.html">Buffer overloads: the big security hole | Tech News on ZDNet</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<p class="description">Buffer Overflow 101 for dummies.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutorial">tutorial</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/s%25C3%25A9curit%25C3%25A9">sécurité</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057951936">Copy</a> | 
<a href="http://blogmarks.net/link/2871380">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/BlueVoodoo/mark/1057737945">
<title>Rational AppScan Standard Ed. V7.7 Trial</title>
<link>http://www.ibm.com/developerworks/downloads/r/appscan/learn.html?S_TACT=105AGX59&amp;S_CMP=DLDTA-c4c-dta&amp;ca=dgr-c4c-dta-btw15appscan77</link>
<description>Download a free trial of IBM Rational AppScan Standard Edition V7.7, previously known as Watchfire AppScan, a leading Web application security testing tool that automates vulnerability assessments and scans and tests for all common Web application vulnerabilities including SQL-injection, cross-site scripting and buffer overflow.</description>
<dc:date>2008-03-14T19:15:37Z</dc:date>
<dc:author>BlueVoodoo</dc:author>
<dc:subject>programming, unix, linux</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/downloads/r/appscan/learn.html?S_TACT=105AGX59&amp;S_CMP=DLDTA-c4c-dta&amp;ca=dgr-c4c-dta-btw15appscan77"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/downloads/r/appscan/learn.html?S_TACT=105AGX59&amp;S_CMP=DLDTA-c4c-dta&amp;ca=dgr-c4c-dta-btw15appscan77">Rational AppScan Standard Ed. V7.7 Trial</a></h4>
 
by <a href="http://blogmarks.net/user/BlueVoodoo">BlueVoodoo</a> 
<p class="description">Download a free trial of IBM Rational AppScan Standard Edition V7.7, previously known as Watchfire AppScan, a leading Web application security testing tool that automates vulnerability assessments and scans and tests for all common Web application vulnerabilities including SQL-injection, cross-site scripting and buffer overflow.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
<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/linux">linux</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057737945">Copy</a> | 
<a href="http://blogmarks.net/link/2703617">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/cascamorto/mark/1057600789">
<title>Category:OWASP Guide Project - OWASP</title>
<link>http://www.owasp.org/index.php/OWASP_Guide_Project</link>
<description>    * 1 Frontispiece
    * 2 About The Open Web Application Security Project
    * 3 Introduction
    * 4 What are web applications?
    * 5 Policy Frameworks
    * 6 Secure Coding Principles
    * 7 Threat Risk Modeling
    * 8 Handling E-Commerce Payments
    * 9 Phishing
    * 10 Web Services
    * 11 Ajax and Other &quot;Rich&quot; Interface Technologies
    * 12 Guide to Authentication
    * 13 Guide to Authorization
    * 14 Session Management
    * 15 Data Validation
    * 16 Interpreter Injection
    * 17 Canonicalization, locale and Unicode
    * 18 Error Handling, Auditing and Logging
    * 19 File System
    * 20 Distributed Computing
    * 21 Buffer Overflows
    * 22 Administrative Interface
    * 23 Guide to Cryptography
    * 24 Configuration
    * 25 Software Quality Assurance
    * 26 Deployment
    * 27 Maintenance
    * 28 GNU Free Documentation License
    * 29 Reference</description>
<dc:date>2007-12-09T21:50:57Z</dc:date>
<dc:author>cascamorto</dc:author>
<dc:subject>administration, webmasters, tutoriels, telecharger</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.owasp.org/index.php/OWASP_Guide_Project"><img border="0" src="http://blogmarks.net/screenshots/2007/12/09/6c783cfcc8c5d80b0822bbe7a0e8c9f2.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.owasp.org/index.php/OWASP_Guide_Project">Category:OWASP Guide Project - OWASP</a></h4>
 
by <a href="http://blogmarks.net/user/cascamorto">cascamorto</a> 
<p class="description">    * 1 Frontispiece
    * 2 About The Open Web Application Security Project
    * 3 Introduction
    * 4 What are web applications?
    * 5 Policy Frameworks
    * 6 Secure Coding Principles
    * 7 Threat Risk Modeling
    * 8 Handling E-Commerce Payments
    * 9 Phishing
    * 10 Web Services
    * 11 Ajax and Other "Rich" Interface Technologies
    * 12 Guide to Authentication
    * 13 Guide to Authorization
    * 14 Session Management
    * 15 Data Validation
    * 16 Interpreter Injection
    * 17 Canonicalization, locale and Unicode
    * 18 Error Handling, Auditing and Logging
    * 19 File System
    * 20 Distributed Computing
    * 21 Buffer Overflows
    * 22 Administrative Interface
    * 23 Guide to Cryptography
    * 24 Configuration
    * 25 Software Quality Assurance
    * 26 Deployment
    * 27 Maintenance
    * 28 GNU Free Documentation License
    * 29 Reference</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/administration">administration</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webmasters">webmasters</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tutoriels">tutoriels</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/telecharger">telecharger</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057600789">Copy</a> | 
<a href="http://blogmarks.net/link/2582910">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/BlueVoodoo/mark/1057402922">
<title>Logging in multi-threaded apps efficiently with ring buffer</title>
<link>http://www.ibm.com/developerworks/aix/library/au-buffer/?ca=dgr-btw15uxbugring&amp;S_TACT=105AGX59&amp;S_CMP=GRsite-btw15</link>
<description>No software is bug free, and application users can encounter unexpected results during the run time of programs. To analyze and find the cause of problems, logging is a method widely used by programmers. In this article, learn how to use a ring buffer for efficient logging with memory operations in place of file operations.</description>
<dc:date>2007-08-17T17:21:42Z</dc:date>
<dc:author>BlueVoodoo</dc:author>
<dc:subject>programming, linux, unix</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/aix/library/au-buffer/?ca=dgr-btw15uxbugring&amp;S_TACT=105AGX59&amp;S_CMP=GRsite-btw15"><img border="0" src="http://blogmarks.net/screenshots/2007/08/17/aac14f331f7b2b6d30a285990b211c48.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/aix/library/au-buffer/?ca=dgr-btw15uxbugring&amp;S_TACT=105AGX59&amp;S_CMP=GRsite-btw15">Logging in multi-threaded apps efficiently with ring buffer</a></h4>
 
by <a href="http://blogmarks.net/user/BlueVoodoo">BlueVoodoo</a> 
<p class="description">No software is bug free, and application users can encounter unexpected results during the run time of programs. To analyze and find the cause of problems, logging is a method widely used by programmers. In this article, learn how to use a ring buffer for efficient logging with memory operations in place of file operations.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/linux">linux</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unix">unix</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057402922">Copy</a> | 
<a href="http://blogmarks.net/link/2406002">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/benoit/mark/1057399034">
<title>Make your software behave: Preventing buffer overflows</title>
<link>http://www.ibm.com/developerworks/library/s-buffer-defend.html</link>
<description></description>
<dc:date>2007-08-14T16:00:36Z</dc:date>
<dc:author>benoit</dc:author>
<dc:subject>software, c, buffer overflow</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ibm.com/developerworks/library/s-buffer-defend.html"><img border="0" src="http://blogmarks.net/screenshots/2007/08/14/d7b025e9d4f4174063fd049e0d760be8.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ibm.com/developerworks/library/s-buffer-defend.html">Make your software behave: Preventing buffer overflows</a></h4>
 
by <a href="http://blogmarks.net/user/benoit">benoit</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/c">c</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/buffer%2Boverflow">buffer overflow</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057399034">Copy</a> | 
<a href="http://blogmarks.net/link/2402708">React (2)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/sylvainulg/mark/1057390784">
<title>USB Human Interface Device (HID) FAQ</title>
<link>http://www.lvr.com/hidfaq.htm</link>
<description>How can an application request a report using a control transfer?
How can an application send a report using a control transfer?
How can an application request reports using interrupt transfers?
How large is the ReadFile buffer?
Where is the Windows documentation for accessing HIDs?
Why do I receive &quot;CRC Error&quot; when attempting to send a report to my device?
...</description>
<dc:date>2007-08-08T10:23:18Z</dc:date>
<dc:author>sylvainulg</dc:author>
<dc:subject>usb, hid, operating system, os, programming</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.lvr.com/hidfaq.htm"><img border="0" src="http://blogmarks.net/screenshots/2007/08/08/54b92cba2adfc90825e0d61237b33cbf.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.lvr.com/hidfaq.htm">USB Human Interface Device (HID) FAQ</a></h4>
 
by <a href="http://blogmarks.net/user/sylvainulg">sylvainulg</a> 
<p class="description">How can an application request a report using a control transfer?
How can an application send a report using a control transfer?
How can an application request reports using interrupt transfers?
How large is the ReadFile buffer?
Where is the Windows documentation for accessing HIDs?
Why do I receive "CRC Error" when attempting to send a report to my device?
...</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/usb">usb</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hid">hid</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/operating%2Bsystem">operating system</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/os">os</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/programming">programming</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057390784">Copy</a> | 
<a href="http://blogmarks.net/link/2395611">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/wrijneveld/mark/1057669607">
<title>Fair trade in tropical crops is possible</title>
<link>http://ase.tufts.edu/gdae/Pubs/rp/KoningCaloFairtradeICAs2004.pdf</link>
<description>plea for making commodity trade fair. UNCTAD policies of buffer stocks did not collapse bc of sconomic but bc of political reasons</description>
<dc:date>2007-07-23T14:07:12Z</dc:date>
<dc:author>wrijneveld</dc:author>
<dc:subject>fairtrade, Econdevelopment, Agriculture</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://ase.tufts.edu/gdae/Pubs/rp/KoningCaloFairtradeICAs2004.pdf"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://ase.tufts.edu/gdae/Pubs/rp/KoningCaloFairtradeICAs2004.pdf">Fair trade in tropical crops is possible</a></h4>
 
by <a href="http://blogmarks.net/user/wrijneveld">wrijneveld</a> 
<p class="description">plea for making commodity trade fair. UNCTAD policies of buffer stocks did not collapse bc of sconomic but bc of political reasons</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fairtrade">fairtrade</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Econdevelopment">Econdevelopment</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Agriculture">Agriculture</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057669607">Copy</a> | 
<a href="http://blogmarks.net/link/2644810">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/chunmin/mark/2689373">
<title>HD Tune website</title>
<link>http://www.hdtune.com/main.html</link>
<description>Hard disk utility which has the following functions: Benchmark: measures the raw performance.  Hard Disk information which includes partition information, supported features, firmware version, serial number, disk capacity, buffer size, transfer mode.</description>
<dc:date>2007-05-10T00:26:54Z</dc:date>
<dc:author>chunmin</dc:author>
<dc:subject>english, freeware, tool, windows</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.hdtune.com/main.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.hdtune.com/main.html">HD Tune website</a></h4>
 
by <a href="http://blogmarks.net/user/chunmin">chunmin</a> 
<p class="description">Hard disk utility which has the following functions: Benchmark: measures the raw performance.  Hard Disk information which includes partition information, supported features, firmware version, serial number, disk capacity, buffer size, transfer mode.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/english">english</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/tool">tool</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/windows">windows</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=2689373">Copy</a> | 
<a href="http://blogmarks.net/link/2213763">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/phumblot/mark/1910929">
<title>Improving Ajax applications for JAWS users</title>
<link>http://juicystudio.com/article/improving-ajax-applications-for-jaws-users.php</link>
<description>
Popular screen readers use a virtual buffer to allow users to interact with web content. This article uncovers undocumented behaviour in JAWS 7.1 and later, which allows web developers to build Ajax applications that update the virtual buffer without any interaction from the user</description>
<dc:date>2007-02-01T13:23:01Z</dc:date>
<dc:author>phumblot</dc:author>
<dc:subject>ajax, accessibility, screen reader</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://juicystudio.com/article/improving-ajax-applications-for-jaws-users.php"><img border="0" src="http://blogmarks.net/screenshots/2007/02/01/eb37d779c5fee8714eb69a104a59472b.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://juicystudio.com/article/improving-ajax-applications-for-jaws-users.php">Improving Ajax applications for JAWS users</a></h4>
 
by <a href="http://blogmarks.net/user/phumblot">phumblot</a> 
<p class="description">
Popular screen readers use a virtual buffer to allow users to interact with web content. This article uncovers undocumented behaviour in JAWS 7.1 and later, which allows web developers to build Ajax applications that update the virtual buffer without any interaction from the user</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ajax">ajax</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/accessibility">accessibility</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/screen%2Breader">screen reader</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1910929">Copy</a> | 
<a href="http://blogmarks.net/link/1631272">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ionobelisk/mark/1878672">
<title>Log Buffer #7: a Carnival of the Vanities for DBAs</title>
<link>http://www.pythian.com/blogs/239/log-buffer-7-a-carnival-of-the-vanities-for-dbas</link>
<description>Lots of bits &amp; pieces for database folx</description>
<dc:date>2007-01-29T10:45:51Z</dc:date>
<dc:author>ionobelisk</dc:author>
<dc:subject>database, db2, oracl, sql</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.pythian.com/blogs/239/log-buffer-7-a-carnival-of-the-vanities-for-dbas"><img border="0" src="http://blogmarks.net/screenshots/2007/01/29/a09410fa01953c47e1fcee8a2a7cae5d.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.pythian.com/blogs/239/log-buffer-7-a-carnival-of-the-vanities-for-dbas">Log Buffer #7: a Carnival of the Vanities for DBAs</a></h4>
 
by <a href="http://blogmarks.net/user/ionobelisk">ionobelisk</a> 
<p class="description">Lots of bits & pieces for database folx</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/db2">db2</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/oracl">oracl</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sql">sql</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1878672">Copy</a> | 
<a href="http://blogmarks.net/link/1608598">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/pvergain/mark/1741894">
<title>Ddrescue - GNU Project - Free Software Foundation (FSF)</title>
<link>http://www.gnu.org/software/ddrescue/ddrescue.html</link>
<description>GNU ddrescue is a data recovery tool. It copies data from one file or block device (hard disc, cdrom, etc) to another, trying hard to rescue data in case of read errors.

Ddrescue does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps.

The basic operation of ddrescue is fully automatic. That is, you don't have to wait for an error, stop the program, read the log, run it in reverse mode, etc.

If you use the logfile feature of ddrescue, the data is rescued very efficiently (only the needed blocks are read). Also you can interrupt the rescue at any time and resume it later at the same point.

Automatic merging of backups: If you have two or more damaged copies of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file. This is so because the probability of having damaged areas at the same places on different input files is very low. Using the logfile, only the needed blocks are read from the second and successive copies.

The logfile is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying.

Also, the same logfile can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets.

Ddrescue aligns its I/O buffer to the sector size so that it can be used to read from raw devices. For efficiency reasons, also aligns it to the memory page size if page size is a multiple of sector size.
</description>
<dc:date>2007-01-11T14:46:36Z</dc:date>
<dc:author>pvergain</dc:author>
<dc:subject>logiciel libre, tools, sauvegarde, ddrescue</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.gnu.org/software/ddrescue/ddrescue.html"><img border="0" src="http://blogmarks.net/screenshots/2007/01/11/201cfe2ff3b5669115ef339bed6d9186.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.gnu.org/software/ddrescue/ddrescue.html">Ddrescue - GNU Project - Free Software Foundation (FSF)</a></h4>
 
by <a href="http://blogmarks.net/user/pvergain">pvergain</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1196492">2 other(s)</a> 
<p class="description">GNU ddrescue is a data recovery tool. It copies data from one file or block device (hard disc, cdrom, etc) to another, trying hard to rescue data in case of read errors.

Ddrescue does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps.

The basic operation of ddrescue is fully automatic. That is, you don't have to wait for an error, stop the program, read the log, run it in reverse mode, etc.

If you use the logfile feature of ddrescue, the data is rescued very efficiently (only the needed blocks are read). Also you can interrupt the rescue at any time and resume it later at the same point.

Automatic merging of backups: If you have two or more damaged copies of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file. This is so because the probability of having damaged areas at the same places on different input files is very low. Using the logfile, only the needed blocks are read from the second and successive copies.

The logfile is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying.

Also, the same logfile can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets.

Ddrescue aligns its I/O buffer to the sector size so that it can be used to read from raw devices. For efficiency reasons, also aligns it to the memory page size if page size is a multiple of sector size.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/logiciel%2Blibre">logiciel libre</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tools">tools</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sauvegarde">sauvegarde</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ddrescue">ddrescue</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1741894">Copy</a> | 
<a href="http://blogmarks.net/link/1196492">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/chachapoya/mark/1258257">
<title>SourceForge.net: kses - PHP HTML/XHTML filter</title>
<link>http://sourceforge.net/projects/kses</link>
<description>kses is an HTML/XHTML filter written in PHP. It removes all unwanted HTML elements and attributes, and it also does several checks on attribute values. kses can be used to avoid Cross-Site Scripting (XSS), Buffer Overflows and Denial of Service attacks.</description>
<dc:date>2006-11-24T13:31:47Z</dc:date>
<dc:author>chachapoya</dc:author>
<dc:subject>php</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://sourceforge.net/projects/kses"><img border="0" src="http://blogmarks.net/screenshots/2006/11/24/870d02deb94ca5c7eb5c1d58d95a320e.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://sourceforge.net/projects/kses">SourceForge.net: kses - PHP HTML/XHTML filter</a></h4>
 
by <a href="http://blogmarks.net/user/chachapoya">chachapoya</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/171042">3 other(s)</a> 
<p class="description">kses is an HTML/XHTML filter written in PHP. It removes all unwanted HTML elements and attributes, and it also does several checks on attribute values. kses can be used to avoid Cross-Site Scripting (XSS), Buffer Overflows and Denial of Service attacks.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/php">php</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1258257">Copy</a> | 
<a href="http://blogmarks.net/link/171042">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ogrisel/mark/1135501">
<title>Ddrescue - GNU Project - Free Software Foundation (FSF)</title>
<link>http://www.gnu.org/software/ddrescue/ddrescue.html</link>
<description>GNU ddrescue is a data recovery tool. It copies data from one file or block device (hard disc, cdrom, etc) to another, trying hard to rescue data in case of read errors.

Ddrescue does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps.

The basic operation of ddrescue is fully automatic. That is, you don't have to wait for an error, stop the program, read the log, run it in reverse mode, etc.

If you use the logfile feature of ddrescue, the data is rescued very efficiently (only the needed blocks are read). Also you can interrupt the rescue at any time and resume it later at the same point.

Automatic merging of backups: If you have two or more damaged copies of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file. This is so because the probability of having damaged areas at the same places on different input files is very low. Using the logfile, only the needed blocks are read from the second and successive copies.

The logfile is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying.

Also, the same logfile can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets.

Ddrescue aligns its I/O buffer to the sector size so that it can be used to read from raw devices. For efficiency reasons, also aligns it to the memory page size if page size is a multiple of sector size.
</description>
<dc:date>2006-10-24T10:06:02Z</dc:date>
<dc:author>ogrisel</dc:author>
<dc:subject>recovery, file, disk, harddisk, automatic</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.gnu.org/software/ddrescue/ddrescue.html"><img border="0" src="http://blogmarks.net/screenshots/2007/01/11/201cfe2ff3b5669115ef339bed6d9186.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.gnu.org/software/ddrescue/ddrescue.html">Ddrescue - GNU Project - Free Software Foundation (FSF)</a></h4>
 
by <a href="http://blogmarks.net/user/ogrisel">ogrisel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/1196492">2 other(s)</a> 
<p class="description">GNU ddrescue is a data recovery tool. It copies data from one file or block device (hard disc, cdrom, etc) to another, trying hard to rescue data in case of read errors.

Ddrescue does not truncate the output file if not asked to. So, every time you run it on the same output file, it tries to fill in the gaps.

The basic operation of ddrescue is fully automatic. That is, you don't have to wait for an error, stop the program, read the log, run it in reverse mode, etc.

If you use the logfile feature of ddrescue, the data is rescued very efficiently (only the needed blocks are read). Also you can interrupt the rescue at any time and resume it later at the same point.

Automatic merging of backups: If you have two or more damaged copies of a file, cdrom, etc, and run ddrescue on all of them, one at a time, with the same output file, you will probably obtain a complete and error-free file. This is so because the probability of having damaged areas at the same places on different input files is very low. Using the logfile, only the needed blocks are read from the second and successive copies.

The logfile is periodically saved to disc. So in case of a crash you can resume the rescue with little recopying.

Also, the same logfile can be used for multiple commands that copy different areas of the file, and for multiple recovery attempts over different subsets.

Ddrescue aligns its I/O buffer to the sector size so that it can be used to read from raw devices. For efficiency reasons, also aligns it to the memory page size if page size is a multiple of sector size.
</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/recovery">recovery</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/file">file</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/disk">disk</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/harddisk">harddisk</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/automatic">automatic</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1135501">Copy</a> | 
<a href="http://blogmarks.net/link/1196492">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/YukuanMark/mark/1146389">
<title>matplotli.mathtext</title>
<link>http://matplotlib.sourceforge.net/matplotlib.mathtext.html</link>
<description>mathtext is a module for parsing TeX expressions and drawing them into a matplotlib.ft2font image buffer. You can draw from this buffer into your backend.</description>
<dc:date>2006-09-03T18:10:20Z</dc:date>
<dc:author>YukuanMark</dc:author>
<dc:subject>python, Matplotlib, plot, numeric, visualization</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://matplotlib.sourceforge.net/matplotlib.mathtext.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://matplotlib.sourceforge.net/matplotlib.mathtext.html">matplotli.mathtext</a></h4>
 
by <a href="http://blogmarks.net/user/YukuanMark">YukuanMark</a> 
<p class="description">mathtext is a module for parsing TeX expressions and drawing them into a matplotlib.ft2font image buffer. You can draw from this buffer into your backend.</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/Matplotlib">Matplotlib</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plot">plot</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/numeric">numeric</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/visualization">visualization</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1146389">Copy</a> | 
<a href="http://blogmarks.net/link/1198315">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ms_michel/mark/647821">
<title>mapguide: MapGuide Open Source</title>
<link>https://mapguide.osgeo.org/</link>
<description>MapGuide Open Source is a web-based platform that enables users to quickly develop and deploy web mapping applications and geospatial web services. MapGuide features an interactive viewer that includes support for feature selection, property inspection, map tips, and operations such as buffer, select within, and measure. MapGuide includes an XML database for managing content, and supports most popular geospatial file formats, databases, and standards. MapGuide can be deployed on Linux or Windows, supports Apache and IIS web servers, and offers extensive PHP, .NET, Java, and JavaScript APIs for application development. MapGuide Open Source is licensed under the LGPL.</description>
<dc:date>2006-06-22T13:16:49Z</dc:date>
<dc:author>ms_michel</dc:author>
<dc:subject>map</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://mapguide.osgeo.org/"><img border="0" src="http://www.blogmarks.net/screenshots/2006/06/22/a47c9056c168271b6fcae36e0444a9b3.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://mapguide.osgeo.org/">mapguide: MapGuide Open Source</a></h4>
 
by <a href="http://blogmarks.net/user/ms_michel">ms_michel</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/935384">1 other(s)</a> 
<p class="description">MapGuide Open Source is a web-based platform that enables users to quickly develop and deploy web mapping applications and geospatial web services. MapGuide features an interactive viewer that includes support for feature selection, property inspection, map tips, and operations such as buffer, select within, and measure. MapGuide includes an XML database for managing content, and supports most popular geospatial file formats, databases, and standards. MapGuide can be deployed on Linux or Windows, supports Apache and IIS web servers, and offers extensive PHP, .NET, Java, and JavaScript APIs for application development. MapGuide Open Source is licensed under the LGPL.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/map">map</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=647821">Copy</a> | 
<a href="http://blogmarks.net/link/935384">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/stan/mark/647792">
<title>mapguide: MapGuide Open Source</title>
<link>https://mapguide.osgeo.org/</link>
<description>MapGuide Open Source is a web-based platform that enables users to quickly develop and deploy web mapping applications and geospatial web services. MapGuide features an interactive viewer that includes support for feature selection, property inspection, map tips, and operations such as buffer, select within, and measure. MapGuide includes an XML database for managing content, and supports most popular geospatial file formats, databases, and standards. MapGuide can be deployed on Linux or Windows, supports Apache and IIS web servers, and offers extensive PHP, .NET, Java, and JavaScript APIs for application development. MapGuide Open Source is licensed under the LGPL.</description>
<dc:date>2006-06-22T12:30:00Z</dc:date>
<dc:author>stan</dc:author>
<dc:subject>map, guide, geo, sig, geospatial, web, mapping, lgpl</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="https://mapguide.osgeo.org/"><img border="0" src="http://www.blogmarks.net/screenshots/2006/06/22/a47c9056c168271b6fcae36e0444a9b3.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="https://mapguide.osgeo.org/">mapguide: MapGuide Open Source</a></h4>
 
by <a href="http://blogmarks.net/user/stan">stan</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/935384">1 other(s)</a> 
<p class="description">MapGuide Open Source is a web-based platform that enables users to quickly develop and deploy web mapping applications and geospatial web services. MapGuide features an interactive viewer that includes support for feature selection, property inspection, map tips, and operations such as buffer, select within, and measure. MapGuide includes an XML database for managing content, and supports most popular geospatial file formats, databases, and standards. MapGuide can be deployed on Linux or Windows, supports Apache and IIS web servers, and offers extensive PHP, .NET, Java, and JavaScript APIs for application development. MapGuide Open Source is licensed under the LGPL.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/map">map</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/guide">guide</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geo">geo</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sig">sig</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/geospatial">geospatial</a>
<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/mapping">mapping</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lgpl">lgpl</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=647792">Copy</a> | 
<a href="http://blogmarks.net/link/935384">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/fakechris/mark/1252850">
<title>DieHard</title>
<link>http://www.cs.umass.edu/~emery/diehard/#Details</link>
<description>DieHard prevents invalid and multiple frees and heap corruption, and probabilistically avoids buffer overflows, dangling pointer errors, and uninitialized reads.</description>
<dc:date>2006-06-05T09:58:24Z</dc:date>
<dc:author>fakechris</dc:author>
<dc:subject>memory</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.cs.umass.edu/~emery/diehard/#Details"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.cs.umass.edu/~emery/diehard/#Details">DieHard</a></h4>
 
by <a href="http://blogmarks.net/user/fakechris">fakechris</a> 
<p class="description">DieHard prevents invalid and multiple frees and heap corruption, and probabilistically avoids buffer overflows, dangling pointer errors, and uninitialized reads.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/memory">memory</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1252850">Copy</a> | 
<a href="http://blogmarks.net/link/1272806">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/taizo_onexone/mark/668345">
<title>odz buffer - 今日のlivedoor Reader</title>
<link>http://d.hatena.ne.jp/odz/20060522/1148354756</link>
<description></description>
<dc:date>2006-05-23T15:43:30Z</dc:date>
<dc:author>taizo_onexone</dc:author>
<dc:subject>reader, plagger</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://d.hatena.ne.jp/odz/20060522/1148354756"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://d.hatena.ne.jp/odz/20060522/1148354756">odz buffer - 今日のlivedoor Reader</a></h4>
 
by <a href="http://blogmarks.net/user/taizo_onexone">taizo_onexone</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/reader">reader</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/plagger">plagger</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=668345">Copy</a> | 
<a href="http://blogmarks.net/link/947487">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/jambe/mark/1976983">
<title>podcast about buffer overflows</title>
<link>http://aolradio.podcast.aol.com/sn/SN-039.mp3</link>
<description></description>
<dc:date>2006-05-12T11:51:59Z</dc:date>
<dc:author>jambe</dc:author>
<dc:subject>podcast, security</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://aolradio.podcast.aol.com/sn/SN-039.mp3"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://aolradio.podcast.aol.com/sn/SN-039.mp3">podcast about buffer overflows</a></h4>
 
by <a href="http://blogmarks.net/user/jambe">jambe</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/podcast">podcast</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/security">security</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1976983">Copy</a> | 
<a href="http://blogmarks.net/link/1685369">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/FredB/mark/1368210">
<title>MacNN Forums : OS X 10.1 window buffer compre...</title>
<link>http://newforums.macnn.com/cgi-bin/ultimatebb.cgi?ubb=get_topic</link>
<description></description>
<dc:date>2006-05-01T02:24:17Z</dc:date>
<dc:author>FredB</dc:author>
<dc:subject>forum, mac, apple</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://newforums.macnn.com/cgi-bin/ultimatebb.cgi?ubb=get_topic"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://newforums.macnn.com/cgi-bin/ultimatebb.cgi?ubb=get_topic">MacNN Forums : OS X 10.1 window buffer compre...</a></h4>
 
by <a href="http://blogmarks.net/user/FredB">FredB</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/forum">forum</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mac">mac</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apple">apple</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1368210">Copy</a> | 
<a href="http://blogmarks.net/link/1352791">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>