<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Clickmaps in sourceforge</title>
	<atom:link href="http://blog.corunet.com/clickmaps-in-sourceforge/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.corunet.com/clickmaps-in-sourceforge/</link>
	<description>Web development, usability and more</description>
	<lastBuildDate>Sun, 28 Feb 2010 21:24:34 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: david</title>
		<link>http://blog.corunet.com/clickmaps-in-sourceforge/comment-page-1/#comment-110</link>
		<dc:creator>david</dc:creator>
		<pubDate>Fri, 16 Mar 2007 14:52:37 +0000</pubDate>
		<guid isPermaLink="false">http://blog.corunet.com/english/clickmaps-in-sourceforge#comment-110</guid>
		<description>Hi Nico,

I haven&#039;t used the RMagick version extensivelly in a production environment. As I stated, it was only made as a proof of concept. We already have a C version that works about 20 thousand clicks a second and up to ten million clicks, that was developed for a customer and internal use.

Anyhow, the main problem with the RMagick version is that it uses too much resources once there are many dots. The previous version, while much slower, was more solid since it saves the in-between images for each dot drawn. The best idea is to adapt the RMagick version so that it splits the dots in about 100-dots groups and work over them, or, otherwise, aplly the same approach we did and wite an standalone version (or license ours) to have enterprise-grade results.</description>
		<content:encoded><![CDATA[<p>Hi Nico,</p>
<p>I haven&#8217;t used the RMagick version extensivelly in a production environment. As I stated, it was only made as a proof of concept. We already have a C version that works about 20 thousand clicks a second and up to ten million clicks, that was developed for a customer and internal use.</p>
<p>Anyhow, the main problem with the RMagick version is that it uses too much resources once there are many dots. The previous version, while much slower, was more solid since it saves the in-between images for each dot drawn. The best idea is to adapt the RMagick version so that it splits the dots in about 100-dots groups and work over them, or, otherwise, aplly the same approach we did and wite an standalone version (or license ours) to have enterprise-grade results.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nico</title>
		<link>http://blog.corunet.com/clickmaps-in-sourceforge/comment-page-1/#comment-109</link>
		<dc:creator>Nico</dc:creator>
		<pubDate>Fri, 16 Mar 2007 11:21:52 +0000</pubDate>
		<guid isPermaLink="false">http://blog.corunet.com/english/clickmaps-in-sourceforge#comment-109</guid>
		<description>Hi,
Sorry but I tried this using RMagick and for me, it&#039;s only usable with logs sporting about nine hundred clicks per page, not more..
Have you got an idea?
Thank you</description>
		<content:encoded><![CDATA[<p>Hi,<br />
Sorry but I tried this using RMagick and for me, it&#8217;s only usable with logs sporting about nine hundred clicks per page, not more..<br />
Have you got an idea?<br />
Thank you</p>
]]></content:encoded>
	</item>
</channel>
</rss>
