<?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/bandwidth">
<title>Public marks with search bandwidth</title>
<description>Public marks with search bandwidth</description>
<link>http://blogmarks.net/marks/search/bandwidth</link>
<items><rdf:Seq><rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058601927"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058591999"/>
<rdf:li resource="http://blogmarks.net/api/user/dzc/mark/1058571250"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058550431"/>
<rdf:li resource="http://blogmarks.net/api/user/karlcow/mark/1058527850"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058596740"/>
<rdf:li resource="http://blogmarks.net/api/user/Spone/mark/1058429957"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058597326"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058597327"/>
<rdf:li resource="http://blogmarks.net/api/user/wabaus/mark/1058297376"/>
<rdf:li resource="http://blogmarks.net/api/user/ycc2106/mark/1058597721"/>
<rdf:li resource="http://blogmarks.net/api/user/ERSWeb/mark/1058228152"/>
<rdf:li resource="http://blogmarks.net/api/user/greut/mark/1058174502"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058205983"/>
<rdf:li resource="http://blogmarks.net/api/user/sbrothier/mark/1058068941"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1058206174"/>
<rdf:li resource="http://blogmarks.net/api/user/camel/mark/1058012855"/>
<rdf:li resource="http://blogmarks.net/api/user/camel/mark/1058002254"/>
<rdf:li resource="http://blogmarks.net/api/user/jdrsantos/mark/1057997049"/>
<rdf:li resource="http://blogmarks.net/api/user/Fiber_Optic/mark/1057981124"/>
<rdf:li resource="http://blogmarks.net/api/user/nicmae/mark/1057961289"/>
<rdf:li resource="http://blogmarks.net/api/user/camel/mark/1057957042"/>
<rdf:li resource="http://blogmarks.net/api/user/garret/mark/1057945316"/>
<rdf:li resource="http://blogmarks.net/api/user/decembre/mark/1057950516"/>
<rdf:li resource="http://blogmarks.net/api/user/jey/mark/1058545412"/>
</rdf:Seq></items>
</channel>
<item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058601927">
<title>Mobile Opportunity: The mobile data apocalypse, and what it means to you</title>
<link>http://mobileopportunity.blogspot.com/2009/11/mobile-data-apocalypse-and-what-it.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;It's also possible to create some APIs that would tell a website how much bandwidth is available to it, so the developer could adjust its features accordingly. This idea is being tossed around between web companies and operators, but I don't know how much is actually being done about it.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-29T11:13:10Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>api, webarchitecture, mobile, webservices</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://mobileopportunity.blogspot.com/2009/11/mobile-data-apocalypse-and-what-it.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://mobileopportunity.blogspot.com/2009/11/mobile-data-apocalypse-and-what-it.html">Mobile Opportunity: The mobile data apocalypse, and what it means to you</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>It's also possible to create some APIs that would tell a website how much bandwidth is available to it, so the developer could adjust its features accordingly. This idea is being tossed around between web companies and operators, but I don't know how much is actually being done about it.</p></blockquote></div>
<p class="tags">
<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/webarchitecture">webarchitecture</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mobile">mobile</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/webservices">webservices</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058601927">Copy</a> | 
<a href="http://blogmarks.net/link/3423131">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058591999">
<title>Internet Explorer and cacheing: beware of the Vary - Crisp's blog</title>
<link>http://crisp.tweakblogs.net/blog/311/internet-explorer-and-cacheing-beware-of-the-vary.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;To cut a long story short: while reconfiguring my local server to match our production settings I found out that the Vary-header was the actual culprit, and that mod_gzip (a module responsible for compressing content before sending it to the client and thus saving bandwidth) added this particular header, even though we explicitly excluded images from being compressed by this module by means of a mimetype filter (images have a mimetype that matches image/* e.g. image/gif, image/jpeg and so on).&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-11-25T14:46:16Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http, implementation</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://crisp.tweakblogs.net/blog/311/internet-explorer-and-cacheing-beware-of-the-vary.html"><img border="0" src="http://blogmarks.net/screenshots/2009/11/25/a3e3f825cdbc905a8070629299e08494.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://crisp.tweakblogs.net/blog/311/internet-explorer-and-cacheing-beware-of-the-vary.html">Internet Explorer and cacheing: beware of the Vary - Crisp's blog</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>To cut a long story short: while reconfiguring my local server to match our production settings I found out that the Vary-header was the actual culprit, and that mod_gzip (a module responsible for compressing content before sending it to the client and thus saving bandwidth) added this particular header, even though we explicitly excluded images from being compressed by this module by means of a mimetype filter (images have a mimetype that matches image/* e.g. image/gif, image/jpeg and so on).</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/implementation">implementation</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058591999">Copy</a> | 
<a href="http://blogmarks.net/link/3416097">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/dzc/mark/1058571250">
<title>Overcome Your Caching Conundrums [Server Side Essentials]</title>
<link>http://articles.sitepoint.com/article/overcome-cache-conundrums</link>
<description>ealing with browser caching is a balancing act. On one hand, you aim to minimize load times and bandwidth use by ensuring that images, scripts, and style sheets are cached by your visitors; however, you still want to ensure that they’re accessing the most recent versions of all your files.

In this article, I’ll show you a few methods for controlling how your site’s files are cached by browsers so you can achieve the best of both worlds: maintaining optimal performance while ensuring that any updates are seen immediately, without a hitch by all of your users.</description>
<dc:date>2009-11-03T15:34:24Z</dc:date>
<dc:author>dzc</dc:author>
<dc:subject>css, image, performance, optimisation, conception web, cache, navigateur</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://articles.sitepoint.com/article/overcome-cache-conundrums"><img border="0" src="http://blogmarks.net/screenshots/2009/11/03/a58cbae6863e4ccdc981f58955828305.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://articles.sitepoint.com/article/overcome-cache-conundrums">Overcome Your Caching Conundrums [Server Side Essentials]</a></h4>
 
by <a href="http://blogmarks.net/user/dzc">dzc</a> 
<p class="description">ealing with browser caching is a balancing act. On one hand, you aim to minimize load times and bandwidth use by ensuring that images, scripts, and style sheets are cached by your visitors; however, you still want to ensure that they’re accessing the most recent versions of all your files.

In this article, I’ll show you a few methods for controlling how your site’s files are cached by browsers so you can achieve the best of both worlds: maintaining optimal performance while ensuring that any updates are seen immediately, without a hitch by all of your users.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/css">css</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/image">image</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/optimisation">optimisation</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/conception%2Bweb">conception web</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cache">cache</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/navigateur">navigateur</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058571250">Copy</a> | 
<a href="http://blogmarks.net/link/3399935">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058550431">
<title>Optimize caching</title>
<link>http://code.google.com/intl/fr/speed/page-speed/docs/caching.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;Most web pages include resources that change infrequently, such as CSS files, image files, JavaScript files, and so on. These resources take time to download over the network, which increases the time it takes to load a web page. HTTP caching allows these resources to be saved, or cached, by a browser or proxy. Once a resource is cached, a browser or proxy can refer to the locally cached copy instead of having to download it again on subsequent visits to the web page. Thus caching is a double win: you reduce round-trip time by eliminating numerous HTTP requests for the required resources, and you substantially reduce the total payload size of the responses. Besides leading to a dramatic reduction in page load time for subsequent user visits, enabling caching can also significantly reduce the bandwidth and hosting costs for your site.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-15T01:53:55Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>http, caching, performance</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://code.google.com/intl/fr/speed/page-speed/docs/caching.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/15/66b26248f4530a54a3af8963827b3052.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://code.google.com/intl/fr/speed/page-speed/docs/caching.html">Optimize caching</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
<div class="description"><blockquote><p>Most web pages include resources that change infrequently, such as CSS files, image files, JavaScript files, and so on. These resources take time to download over the network, which increases the time it takes to load a web page. HTTP caching allows these resources to be saved, or cached, by a browser or proxy. Once a resource is cached, a browser or proxy can refer to the locally cached copy instead of having to download it again on subsequent visits to the web page. Thus caching is a double win: you reduce round-trip time by eliminating numerous HTTP requests for the required resources, and you substantially reduce the total payload size of the responses. Besides leading to a dramatic reduction in page load time for subsequent user visits, enabling caching can also significantly reduce the bandwidth and hosting costs for your site.</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/caching">caching</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/performance">performance</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058550431">Copy</a> | 
<a href="http://blogmarks.net/link/3383771">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/karlcow/mark/1058527850">
<title>An Engineer's Guide to Bandwidth (Yahoo! Developer Network Blog)</title>
<link>http://developer.yahoo.net/blog/archives/2009/10/a_engineers_gui.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;Web app developers spend most of our time not thinking about how data is actually transmitted through the bowels of the network stack. Abstractions at the application layer let us pretend that networks read and write whole messages as smooth streams of bytes. Generally this is a good thing. But knowing what's going underneath is crucial to performance tuning and application design. The character of our users' internet connections is changing and some of the rules of thumb we rely on may need to be revised.&lt;/p&gt;&lt;/blockquote&gt;</description>
<dc:date>2009-10-02T03:34:58Z</dc:date>
<dc:author>karlcow</dc:author>
<dc:subject>bandwidth</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://developer.yahoo.net/blog/archives/2009/10/a_engineers_gui.html"><img border="0" src="http://blogmarks.net/screenshots/2009/10/02/dd50fea250ab11f1c2e1db588c0b9416.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://developer.yahoo.net/blog/archives/2009/10/a_engineers_gui.html">An Engineer's Guide to Bandwidth (Yahoo! Developer Network Blog)</a></h4>
 
by <a href="http://blogmarks.net/user/karlcow">karlcow</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3363351">1 other(s)</a> 
<div class="description"><blockquote><p>Web app developers spend most of our time not thinking about how data is actually transmitted through the bowels of the network stack. Abstractions at the application layer let us pretend that networks read and write whole messages as smooth streams of bytes. Generally this is a good thing. But knowing what's going underneath is crucial to performance tuning and application design. The character of our users' internet connections is changing and some of the rules of thumb we rely on may need to be revised.</p></blockquote></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bandwidth">bandwidth</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058527850">Copy</a> | 
<a href="http://blogmarks.net/link/3363351">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058596740">
<title>Myspace image hosting , Free Auction Image Hosting , eBay Auction Galleries and Picture Posting</title>
<link>http://xtupload.com/</link>
<description>max size 99999mb, Unlimited Disk Space,  Unlimited Bandwidth, draw, upload by url, by zip. Slideshows</description>
<dc:date>2009-09-22T13:06:15Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>imahe, hosting, free</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://xtupload.com/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://xtupload.com/">Myspace image hosting , Free Auction Image Hosting , eBay Auction Galleries and Picture Posting</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">max size 99999mb, Unlimited Disk Space,  Unlimited Bandwidth, draw, upload by url, by zip. Slideshows</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/imahe">imahe</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hosting">hosting</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/free">free</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058596740">Copy</a> | 
<a href="http://blogmarks.net/link/3420118">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Spone/mark/1058429957">
<title>CamStudio - Free Screen Recording Software</title>
<link>http://camstudio.org/</link>
<description>CamStudio is able to record all screen and audio activity on your computer and create industry-standard AVI video files and using its built-in SWF Producer can turn those AVIs into lean, mean, bandwidth-friendly Streaming Flash videos (SWFs) </description>
<dc:date>2009-07-16T13:31:40Z</dc:date>
<dc:author>Spone</dc:author>
<dc:subject>flash, video, software, swf, screencast</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://camstudio.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/16/be5e3aadc2e13889bfc39b4c7504bf66.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://camstudio.org/">CamStudio - Free Screen Recording Software</a></h4>
 
by <a href="http://blogmarks.net/user/Spone">Spone</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/729444">10 other(s)</a> 
<p class="description">CamStudio is able to record all screen and audio activity on your computer and create industry-standard AVI video files and using its built-in SWF Producer can turn those AVIs into lean, mean, bandwidth-friendly Streaming Flash videos (SWFs) </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/flash">flash</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/video">video</a>
<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/swf">swf</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/screencast">screencast</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058429957">Copy</a> | 
<a href="http://blogmarks.net/link/729444">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058597326">
<title>Online Backup - IDrive - Encrypted, Secure and Automated!</title>
<link>http://www.idrive.com/</link>
<description>IDrive offers 2GB of free online backup space without any backup and restore restrictions or bandwidth limits or file type restrictions.</description>
<dc:date>2009-06-20T07:58:51Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>backup, online, 2G, free, sync</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.idrive.com/"><img border="0" src="http://blogmarks.net/screenshots/2007/03/09/76fb61a7aff4a5d5ef037c69c7ea782c.png" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.idrive.com/">Online Backup - IDrive - Encrypted, Secure and Automated!</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/635687">5 other(s)</a> 
<p class="description">IDrive offers 2GB of free online backup space without any backup and restore restrictions or bandwidth limits or file type restrictions.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/backup">backup</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/online">online</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/2G">2G</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/free">free</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/sync">sync</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058597326">Copy</a> | 
<a href="http://blogmarks.net/link/635687">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058597327">
<title>Online Backup - IDrive - Encrypted, Secure and Automated!</title>
<link>http://www.idrive.com/idrivee/jsp/index1.jsp</link>
<description>IDrive offers 2GB of free online backup space without any backup and restore restrictions or bandwidth limits or file type restrictions.</description>
<dc:date>2009-06-20T07:57:11Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>backup, online, 2G, free</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.idrive.com/idrivee/jsp/index1.jsp"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.idrive.com/idrivee/jsp/index1.jsp">Online Backup - IDrive - Encrypted, Secure and Automated!</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">IDrive offers 2GB of free online backup space without any backup and restore restrictions or bandwidth limits or file type restrictions.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/backup">backup</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/online">online</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/2G">2G</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/free">free</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058597327">Copy</a> | 
<a href="http://blogmarks.net/link/3420480">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/wabaus/mark/1058297376">
<title>zer01mobile unlimited cell service</title>
<link>http://www.zer01mobile.com/</link>
<description>Unlimited calls and bandwidth for $69.95/mo. on a smart phone.  No contract.  Pay month-to-month.</description>
<dc:date>2009-04-24T16:20:23Z</dc:date>
<dc:author>wabaus</dc:author>
<dc:subject>cell, unlimited, bandwidth</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.zer01mobile.com/"><img border="0" src="http://blogmarks.net/screenshots/2009/04/24/70e25cb4858cb2c6db335ac87cd4e17e.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.zer01mobile.com/">zer01mobile unlimited cell service</a></h4>
 
by <a href="http://blogmarks.net/user/wabaus">wabaus</a> 
<p class="description">Unlimited calls and bandwidth for $69.95/mo. on a smart phone.  No contract.  Pay month-to-month.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cell">cell</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/unlimited">unlimited</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bandwidth">bandwidth</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058297376">Copy</a> | 
<a href="http://blogmarks.net/link/3173856">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ycc2106/mark/1058597721">
<title>IntrArts Creative Media - throttled</title>
<link>http://www.intrarts.com/throttledcli.html</link>
<description>throttled is a bandwidth shaping application for Mac OS X and FreeBSD which allows you to cap your upstream bandwidth, prioritize ACK packets, and keep your download speeds high even when your server is sending out at full speed.</description>
<dc:date>2009-04-07T08:07:34Z</dc:date>
<dc:author>ycc2106</dc:author>
<dc:subject>mac, software, bandwidth, configuration, customize</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.intrarts.com/throttledcli.html"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.intrarts.com/throttledcli.html">IntrArts Creative Media - throttled</a></h4>
 
by <a href="http://blogmarks.net/user/ycc2106">ycc2106</a> 
<p class="description">throttled is a bandwidth shaping application for Mac OS X and FreeBSD which allows you to cap your upstream bandwidth, prioritize ACK packets, and keep your download speeds high even when your server is sending out at full speed.</p>
<p class="tags">
<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/software">software</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bandwidth">bandwidth</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/configuration">configuration</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/customize">customize</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058597721">Copy</a> | 
<a href="http://blogmarks.net/link/3420726">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/ERSWeb/mark/1058228152">
<title>Enabling HTTP Compression in IIS 6.0</title>
<link>http://www.dotnetjunkies.com/Article/16267D49-4C6E-4063-AB12-853761D31E66.dcik</link>
<description>HTTP Compression is a wonderful technology that accomplishes a lot of different things. It allows faster page serving to clients and lower server costs due to lowered bandwidth (these two being enough for me to implement). There are a handful of articles out there that explain how to implement HTTP Compression in Internet Information Server (IIS) 6.0, but I haven’t been able to find a nice step-by-step article, so I decided to set one up. In this how-to, I’ll briefly explain what HTTP Compression is and how it works in IIS 6.0, and then provide step-by-step instructions on how to implement it because it’s not as simple as flipping a switch. In fact, there are many things in multiple places on the server you have to properly configure to implement HTTP Compression. </description>
<dc:date>2009-03-03T22:07:03Z</dc:date>
<dc:author>ERSWeb</dc:author>
<dc:subject>internet, server, technology, this, it, iis, articles</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.dotnetjunkies.com/Article/16267D49-4C6E-4063-AB12-853761D31E66.dcik"><img border="0" src="http://blogmarks.net/screenshots/2009/03/03/d82cd29938b470d5f5d54343cbeed4a2.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.dotnetjunkies.com/Article/16267D49-4C6E-4063-AB12-853761D31E66.dcik">Enabling HTTP Compression in IIS 6.0</a></h4>
 
by <a href="http://blogmarks.net/user/ERSWeb">ERSWeb</a> 
<p class="description">HTTP Compression is a wonderful technology that accomplishes a lot of different things. It allows faster page serving to clients and lower server costs due to lowered bandwidth (these two being enough for me to implement). There are a handful of articles out there that explain how to implement HTTP Compression in Internet Information Server (IIS) 6.0, but I haven’t been able to find a nice step-by-step article, so I decided to set one up. In this how-to, I’ll briefly explain what HTTP Compression is and how it works in IIS 6.0, and then provide step-by-step instructions on how to implement it because it’s not as simple as flipping a switch. In fact, there are many things in multiple places on the server you have to properly configure to implement HTTP Compression. </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/internet">internet</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/technology">technology</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/this">this</a>
<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/iis">iis</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/articles">articles</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058228152">Copy</a> | 
<a href="http://blogmarks.net/link/3116126">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/greut/mark/1058174502">
<title>James Shore: The Decline and Fall of Agile</title>
<link>http://jamesshore.com/Blog/The-Decline-and-Fall-of-Agile.html</link>
<description>&lt;blockquote&gt;&lt;p&gt;Or maybe we need to stop selling Agile. Maybe we need to say, &quot;Agile is hard, and you can't master it by sitting through a two-day course.&quot; Maybe we need to be firm and say, &quot;Sorry, if you don't use agile engineering practices, if you don't have high-bandwidth communication, and if you don't include a strong customer voice, you're not going to succeed. Try something else instead.&quot; Scrum is popular because it's easy--and that's part of the problem.&lt;/p&gt;&lt;/blockquote&gt;&lt;p&gt;Is that linked to the cargo cult thingy?&lt;/p&gt;</description>
<dc:date>2009-01-28T08:20:47Z</dc:date>
<dc:author>greut</dc:author>
<dc:subject>agile, use, scrum, fail, lean, cargo cult</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://jamesshore.com/Blog/The-Decline-and-Fall-of-Agile.html"><img border="0" src="http://blogmarks.net/screenshots/2009/01/28/8792e2a08b9729d873e768ad9fc01a1f.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://jamesshore.com/Blog/The-Decline-and-Fall-of-Agile.html">James Shore: The Decline and Fall of Agile</a></h4>
 
by <a href="http://blogmarks.net/user/greut">greut</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/3068600">1 other(s)</a> 
<div class="description"><blockquote><p>Or maybe we need to stop selling Agile. Maybe we need to say, "Agile is hard, and you can't master it by sitting through a two-day course." Maybe we need to be firm and say, "Sorry, if you don't use agile engineering practices, if you don't have high-bandwidth communication, and if you don't include a strong customer voice, you're not going to succeed. Try something else instead." Scrum is popular because it's easy--and that's part of the problem.</p></blockquote><p>Is that linked to the cargo cult thingy?</p></div>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/agile">agile</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/use">use</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/scrum">scrum</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/fail">fail</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lean">lean</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/cargo%2Bcult">cargo cult</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058174502">Copy</a> | 
<a href="http://blogmarks.net/link/3068600">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058205983">
<title>Featured Download: FilePhile Transfers Any Size File Between Any Two Systems</title>
<link>http://lifehacker.com/5113485/filephile-transfers-any-size-file-between-any-two-systems</link>
<description>After registering at FilePhile's site with an email address and password, you grab and install a copy of the Java-based app, launch it, and add email addresses to your buddy list. Sending a file is a simple right-click on someone's name, but you can limit the bandwidth eaten up by FilePhile in its preferences. The transfers themselves are encrypted, and, as the site boasts, can be any size. That's about it, but that's probably all you need.</description>
<dc:date>2008-12-21T17:31:55Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>uploawd, transfers, share, linux, fichier, mac, windows, telecharger, lifehacker, partage, p2p, download, application, online, tool, outil, java</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lifehacker.com/5113485/filephile-transfers-any-size-file-between-any-two-systems"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lifehacker.com/5113485/filephile-transfers-any-size-file-between-any-two-systems">Featured Download: FilePhile Transfers Any Size File Between Any Two Systems</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">After registering at FilePhile's site with an email address and password, you grab and install a copy of the Java-based app, launch it, and add email addresses to your buddy list. Sending a file is a simple right-click on someone's name, but you can limit the bandwidth eaten up by FilePhile in its preferences. The transfers themselves are encrypted, and, as the site boasts, can be any size. That's about it, but that's probably all you need.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/uploawd">uploawd</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/transfers">transfers</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/share">share</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/fichier">fichier</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/windows">windows</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/telecharger">telecharger</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lifehacker">lifehacker</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/partage">partage</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/p2p">p2p</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/download">download</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/application">application</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/online">online</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/outil">outil</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/java">java</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058205983">Copy</a> | 
<a href="http://blogmarks.net/link/3097040">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/sbrothier/mark/1058068941">
<title>Shopify — Hosted e-commerce with style, in less than 2 minutes</title>
<link>http://www.shopify.com/</link>
<description>Selling online with Shopify is easy:

We take care of hosting, bandwidth,
and security, so you can focus on your business.

You are just a few minutes away from
your very own e-commerce store.</description>
<dc:date>2008-11-23T21:42:00Z</dc:date>
<dc:author>sbrothier</dc:author>
<dc:subject>shop, web services</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.shopify.com/"><img border="0" src="http://blogmarks.net/screenshots/2008/11/23/b664976dee5b6c94177ceab6c6798a1b.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.shopify.com/">Shopify — Hosted e-commerce with style, in less than 2 minutes</a></h4>
 
by <a href="http://blogmarks.net/user/sbrothier">sbrothier</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/454194">6 other(s)</a> 
<p class="description">Selling online with Shopify is easy:

We take care of hosting, bandwidth,
and security, so you can focus on your business.

You are just a few minutes away from
your very own e-commerce store.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/shop">shop</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/web%2Bservices">web services</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058068941">Copy</a> | 
<a href="http://blogmarks.net/link/454194">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1058206174">
<title>Routeur Hack____with open-source firmware Tomato____Set Up Universal Ad Blocking Through Your Router</title>
<link>http://lifehacker.com/5060053</link>
<description>&quot;If you've turned your $60 router into a user-friendly super-router with open-source firmware Tomato, you already know that Tomato can boost your Wi-Fi signal, track bandwidth usage, and set Quality of Service rules with ease.&quot;</description>
<dc:date>2008-10-20T23:42:20Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>personnaliser, opensource, wifi, hack, routeur, lifehacker</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://lifehacker.com/5060053"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://lifehacker.com/5060053">Routeur Hack____with open-source firmware Tomato____Set Up Universal Ad Blocking Through Your Router</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">"If you've turned your $60 router into a user-friendly super-router with open-source firmware Tomato, you already know that Tomato can boost your Wi-Fi signal, track bandwidth usage, and set Quality of Service rules with ease."</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/personnaliser">personnaliser</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/wifi">wifi</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/hack">hack</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/routeur">routeur</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/lifehacker">lifehacker</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058206174">Copy</a> | 
<a href="http://blogmarks.net/link/3097201">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/camel/mark/1058012855">
<title>Box Backup - Trac</title>
<link>http://www.boxbackup.org/trac/wiki</link>
<description>Box Backup is an open source, completely automatic, on-line backup system. It has the following key features:

    * All backed up data is stored on the server in files on a filesystem - no tape, archive or other special devices are required. 

    * The server is trusted only to make files available when they are required - all data is encrypted and can be decoded only by the original client. This makes it ideal for backing up over an untrusted network (such as the Internet), or where the server is in an uncontrolled environment. 

    * A backup daemon runs on systems to be backed up, and copies encrypted data to the server when it notices changes - so backups are continuous and up-to-date (although traditional snapshot backups are possible too). 

    * Only changes within files are sent to the server, just like rsync, minimising the bandwidth used between clients and server. This makes it particularly suitable for backing up between distant locations, or over the Internet. 

    * It behaves like tape - old file versions and deleted files are available. 

    * Old versions of files on the server are stored as changes from the current version, minimising the storage space required on the server. Files are the server are also compressed to minimise their size. 

    * Choice of backup behaviour - it can be optimised for document or server backup. 

    * It is designed to be easy and cheap to run a server. It has a portable implementation, and optional RAID implemented in userland for reliability without complex server setup or expensive hardware. 

</description>
<dc:date>2008-10-09T14:59:13Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>server, backup, network, file, setup, box</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.boxbackup.org/trac/wiki"><img border="0" src="http://blogmarks.net/screenshots/2008/10/09/0400d6e387692085db453f6254a54577.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.boxbackup.org/trac/wiki">Box Backup - Trac</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
<p class="description">Box Backup is an open source, completely automatic, on-line backup system. It has the following key features:

    * All backed up data is stored on the server in files on a filesystem - no tape, archive or other special devices are required. 

    * The server is trusted only to make files available when they are required - all data is encrypted and can be decoded only by the original client. This makes it ideal for backing up over an untrusted network (such as the Internet), or where the server is in an uncontrolled environment. 

    * A backup daemon runs on systems to be backed up, and copies encrypted data to the server when it notices changes - so backups are continuous and up-to-date (although traditional snapshot backups are possible too). 

    * Only changes within files are sent to the server, just like rsync, minimising the bandwidth used between clients and server. This makes it particularly suitable for backing up between distant locations, or over the Internet. 

    * It behaves like tape - old file versions and deleted files are available. 

    * Old versions of files on the server are stored as changes from the current version, minimising the storage space required on the server. Files are the server are also compressed to minimise their size. 

    * Choice of backup behaviour - it can be optimised for document or server backup. 

    * It is designed to be easy and cheap to run a server. It has a portable implementation, and optional RAID implemented in userland for reliability without complex server setup or expensive hardware. 

</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/backup">backup</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/network">network</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/setup">setup</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/box">box</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058012855">Copy</a> | 
<a href="http://blogmarks.net/link/2925451">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/camel/mark/1058002254">
<title>Monitoring Bandwidth Usage for a Xen node @ IONCANNON</title>
<link>http://www.ioncannon.net/system-administration/84/monitoring-bandwidth-usage-for-a-xen-node/</link>
<description>After my last post on limiting bandwidth usage on a Xen node I thought I would follow up with how to monitor the bandwidth usage of a Xen node.

I chose to use netacct-mysql to monitor bandwidth and store the results into a mysql database. This isn't the only way of monitoring the bandwidth but it was easy to set up and stores the information directly into mysql without needing any extra scripts.

On the Xen setup I'm using for an example there are 3 nodes and a bucket for each node will be created in the mysql database by netacct. Setting up netacct can be tricky so you will want to check to make sure traffic for each node is going into the correct bucket.</description>
<dc:date>2008-09-29T09:24:52Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>xen, mysql, monitoring, setup, database</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ioncannon.net/system-administration/84/monitoring-bandwidth-usage-for-a-xen-node/"><img border="0" src="http://blogmarks.net/screenshots/2008/09/29/5cd4114e652d6a9f4e397d2dbbde76ad.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ioncannon.net/system-administration/84/monitoring-bandwidth-usage-for-a-xen-node/">Monitoring Bandwidth Usage for a Xen node @ IONCANNON</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
<p class="description">After my last post on limiting bandwidth usage on a Xen node I thought I would follow up with how to monitor the bandwidth usage of a Xen node.

I chose to use netacct-mysql to monitor bandwidth and store the results into a mysql database. This isn't the only way of monitoring the bandwidth but it was easy to set up and stores the information directly into mysql without needing any extra scripts.

On the Xen setup I'm using for an example there are 3 nodes and a bucket for each node will be created in the mysql database by netacct. Setting up netacct can be tricky so you will want to check to make sure traffic for each node is going into the correct bucket.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/xen">xen</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mysql">mysql</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/monitoring">monitoring</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/setup">setup</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/database">database</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058002254">Copy</a> | 
<a href="http://blogmarks.net/link/2915373">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/jdrsantos/mark/1057997049">
<title>Main Page - VbGORE Visual Basic Online RPG Engine</title>
<link>http://www.vbgore.com/Main_Page</link>
<description>vbGORE is a powerful open source and free mmorpg maker / engine in development that concentrates on optimization and orpg engine features. With the help of vbGORE's fast networking and powerful graphics engine and some (although not required) knowledge in game programming in visual basic, you can create the game of your dreams without paying for a ton of bandwidth and a powerful server to support your vb game.</description>
<dc:date>2008-09-19T07:53:53Z</dc:date>
<dc:author>jdrsantos</dc:author>
<dc:subject>games, mmorpg, visual_basic, open_source</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.vbgore.com/Main_Page"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.vbgore.com/Main_Page">Main Page - VbGORE Visual Basic Online RPG Engine</a></h4>
 
by <a href="http://blogmarks.net/user/jdrsantos">jdrsantos</a> 
<p class="description">vbGORE is a powerful open source and free mmorpg maker / engine in development that concentrates on optimization and orpg engine features. With the help of vbGORE's fast networking and powerful graphics engine and some (although not required) knowledge in game programming in visual basic, you can create the game of your dreams without paying for a ton of bandwidth and a powerful server to support your vb game.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/games">games</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mmorpg">mmorpg</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/visual_basic">visual_basic</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/open_source">open_source</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057997049">Copy</a> | 
<a href="http://blogmarks.net/link/2912229">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/Fiber_Optic/mark/1057981124">
<title>Cam Studio</title>
<link>http://camstudio.org/</link>
<description>CamStudio is able to record all screen and audio activity on your computer and create industry-standard AVI video files and using its built-in SWF Producer can turn those AVIs into lean, mean, bandwidth-friendly Streaming Flash videos (SWFs) </description>
<dc:date>2008-09-13T14:14:19Z</dc:date>
<dc:author>Fiber_Optic</dc:author>
<dc:subject>tool</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://camstudio.org/"><img border="0" src="http://blogmarks.net/screenshots/2009/07/16/be5e3aadc2e13889bfc39b4c7504bf66.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://camstudio.org/">Cam Studio</a></h4>
 
by <a href="http://blogmarks.net/user/Fiber_Optic">Fiber_Optic</a> 
 &amp; <a class="public" href="http://blogmarks.net/link/729444">10 other(s)</a> 
<p class="description">CamStudio is able to record all screen and audio activity on your computer and create industry-standard AVI video files and using its built-in SWF Producer can turn those AVIs into lean, mean, bandwidth-friendly Streaming Flash videos (SWFs) </p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tool">tool</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057981124">Copy</a> | 
<a href="http://blogmarks.net/link/729444">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/nicmae/mark/1057961289">
<title>samaxes » .htaccess - gzip and cache your site for faster loading and bandwidth saving</title>
<link>http://www.samaxes.com/2008/04/20/htaccess-gzip-and-cache-your-site-for-faster-loading-and-bandwidth-saving/</link>
<description></description>
<dc:date>2008-08-25T20:43:54Z</dc:date>
<dc:author>nicmae</dc:author>
<dc:subject>apache</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.samaxes.com/2008/04/20/htaccess-gzip-and-cache-your-site-for-faster-loading-and-bandwidth-saving/"><img border="0" src="http://blogmarks.net/screenshots/2008/08/25/0a4bc5188b479f266acf9c2e65651e38.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.samaxes.com/2008/04/20/htaccess-gzip-and-cache-your-site-for-faster-loading-and-bandwidth-saving/">samaxes » .htaccess - gzip and cache your site for faster loading and bandwidth saving</a></h4>
 
by <a href="http://blogmarks.net/user/nicmae">nicmae</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/apache">apache</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057961289">Copy</a> | 
<a href="http://blogmarks.net/link/2879983">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/camel/mark/1057957042">
<title>Throttling qmail SMTP receive bandwidth | www.enchantedage.com</title>
<link>http://www.enchantedage.com/node/10</link>
<description>I wrote the program &quot;throttle.c,&quot; which you can insert into the tcpserver chain of commands for a qmail smtpd server. It takes one argument: the number of kilobytes per second to let through on the incoming file descriptor. Throttle does not throttle the outgoing file descriptor, because that's usually just status from your mail server.

Additionally, throttle will set an alarm, so that any session longer than 15 minutes will expire and disconnect. This affords some amount of protection against lingering sessions that eat up your parallelism limit; I've seen such sessions from presumably trojaned DSL machines connecting to the mail server to send spam.</description>
<dc:date>2008-08-22T08:59:44Z</dc:date>
<dc:author>camel</dc:author>
<dc:subject>server, qmail, mail, file, throttle, bandwidth</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.enchantedage.com/node/10"><img border="0" src="http://blogmarks.net/screenshots/2008/08/22/8a9697a0250c7cb80c38960a772768ef.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.enchantedage.com/node/10">Throttling qmail SMTP receive bandwidth | www.enchantedage.com</a></h4>
 
by <a href="http://blogmarks.net/user/camel">camel</a> 
<p class="description">I wrote the program "throttle.c," which you can insert into the tcpserver chain of commands for a qmail smtpd server. It takes one argument: the number of kilobytes per second to let through on the incoming file descriptor. Throttle does not throttle the outgoing file descriptor, because that's usually just status from your mail server.

Additionally, throttle will set an alarm, so that any session longer than 15 minutes will expire and disconnect. This affords some amount of protection against lingering sessions that eat up your parallelism limit; I've seen such sessions from presumably trojaned DSL machines connecting to the mail server to send spam.</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/server">server</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/qmail">qmail</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/mail">mail</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/throttle">throttle</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/bandwidth">bandwidth</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057957042">Copy</a> | 
<a href="http://blogmarks.net/link/2876060">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/garret/mark/1057945316">
<title>Last FM Open Mind Index | 77</title>
<link>http://www.musickum.com/omi/index.php</link>
<description>&quot;The LastFM Open Mind Index (OMI) is an interesting way to understand your taste in music. The index is a calculation based on your last.fm top artists of the last 12 months. The quantity of your played songs, as well as the artist-tags are reflected in the calculation. A high OMI is an indicator for a high musical bandwidth and your openness for different kind of music.&quot; Rocketsurgeon</description>
<dc:date>2008-08-13T22:03:17Z</dc:date>
<dc:author>garret</dc:author>
<dc:subject>music, music recommendations, audioscrobbler, Last.FM</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.musickum.com/omi/index.php"><img border="0" src="http://blogmarks.net/screenshots/2008/08/13/4ba48e6a01347b4b9c89a00432988132.jpg" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.musickum.com/omi/index.php">Last FM Open Mind Index | 77</a></h4>
 
by <a href="http://blogmarks.net/user/garret">garret</a> 
<p class="description">"The LastFM Open Mind Index (OMI) is an interesting way to understand your taste in music. The index is a calculation based on your last.fm top artists of the last 12 months. The quantity of your played songs, as well as the artist-tags are reflected in the calculation. A high OMI is an indicator for a high musical bandwidth and your openness for different kind of music." Rocketsurgeon</p>
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/music">music</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/music%2Brecommendations">music recommendations</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/audioscrobbler">audioscrobbler</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/Last.FM">Last.FM</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057945316">Copy</a> | 
<a href="http://blogmarks.net/link/2865415">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/decembre/mark/1057950516">
<title>bibliotheque OPAC.02 : Une experience pour avoir Google comme moteur de recherche dans l'opac (Get Tooled Up : 'Looking for a Google Box?')</title>
<link>http://www.ariadne.ac.uk/issue42/rahtz/</link>
<description>There are, perhaps, four directions we can take:
   1. Evaluate the complete range of closed and open source offerings, pick the best, and be prepared to pay a yearly licence fee of an unknown amount
   2. Develop our own private search engine, possibly based on ht://Dig [3] or egothor [4] code
   3. Make use of the free Google index of our pages
   4. License Google technology to do local indexing

Each route has its attractions, but the latter two are particularly attractive because of the high degree of trust in, and familiarity with, Google. But the public search has problems:

    * Google cannot see inside our protected sites
    * Every search transaction has to leave our site, is dependent on international networks, and uses up bandwidth
    * The depth and frequency of search is not guaranteed
    * Google may withdraw the service at any time</description>
<dc:date>2008-08-12T09:28:41Z</dc:date>
<dc:author>decembre</dc:author>
<dc:subject>google, bib, experience, tester, recherche, horizon, opac2.0</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://www.ariadne.ac.uk/issue42/rahtz/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://www.ariadne.ac.uk/issue42/rahtz/">bibliotheque OPAC.02 : Une experience pour avoir Google comme moteur de recherche dans l'opac (Get Tooled Up : 'Looking for a Google Box?')</a></h4>
 
by <a href="http://blogmarks.net/user/decembre">decembre</a> 
<p class="description">There are, perhaps, four directions we can take:
   1. Evaluate the complete range of closed and open source offerings, pick the best, and be prepared to pay a yearly licence fee of an unknown amount
   2. Develop our own private search engine, possibly based on ht://Dig [3] or egothor [4] code
   3. Make use of the free Google index of our pages
   4. License Google technology to do local indexing

Each route has its attractions, but the latter two are particularly attractive because of the high degree of trust in, and familiarity with, Google. But the public search has problems:

    * Google cannot see inside our protected sites
    * Every search transaction has to leave our site, is dependent on international networks, and uses up bandwidth
    * The depth and frequency of search is not guaranteed
    * Google may withdraw the service at any time</p>
<p class="tags">
<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/bib">bib</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/experience">experience</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/tester">tester</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/recherche">recherche</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/horizon">horizon</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/opac2.0">opac2.0</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1057950516">Copy</a> | 
<a href="http://blogmarks.net/link/2870078">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> <item rdf:about="http://blogmarks.net/api/user/jey/mark/1058545412">
<title>Network Monitoring, Application Monitoring, Bandwidth Monitoring, Wireless Monitoring and Asset Management - AdventNet Inc</title>
<link>http://manageengine.adventnet.com/</link>
<description></description>
<dc:date>2008-07-29T17:51:55Z</dc:date>
<dc:author>jey</dc:author>
<dc:subject>ApplicationMonitoring, NetworkManagement, monitoring</dc:subject>
<content:encoded><![CDATA[<div class="mark">
<a href="http://manageengine.adventnet.com/"><img border="0" src="http://blogmarks.net/screenshots/404.php" alt="" /></a>
<div class="xfolkentry">
<h4><a class="taggedlink" href="http://manageengine.adventnet.com/">Network Monitoring, Application Monitoring, Bandwidth Monitoring, Wireless Monitoring and Asset Management - AdventNet Inc</a></h4>
 
by <a href="http://blogmarks.net/user/jey">jey</a> 
<p class="tags">
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/ApplicationMonitoring">ApplicationMonitoring</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/NetworkManagement">NetworkManagement</a>
<a rel="tag" class="tag public_tag" href="http://blogmarks.net/marks/tag/monitoring">monitoring</a>
</p>
<div class="action-bar">
<a href="http://blogmarks.net/my/marks,new?id=1058545412">Copy</a> | 
<a href="http://blogmarks.net/link/3379553">React (0)</a></div>
</div>
</div>
]]></content:encoded>
</item> </rdf:RDF>