<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.3.1" -->
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	>
<channel>
	<title>Comments on: Evaluating Terracotta</title>
	<link>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/</link>
	<description>Mumbling about software</description>
	<pubDate>Thu, 11 Mar 2010 03:25:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.3.1</generator>
		<item>
		<title>By: Kevin Clark</title>
		<link>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-512</link>
		<dc:creator>Kevin Clark</dc:creator>
		<pubDate>Thu, 12 Mar 2009 11:01:35 +0000</pubDate>
		<guid>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-512</guid>
		<description>hi,

although NCache is not basically a java player but i think it has some very nice features that any distributed caching enthusiast would like. It also has a free version called NCache Express. Although this product is in .net domain but it works well with java too.</description>
		<content:encoded><![CDATA[<p>hi,</p>
<p>although NCache is not basically a java player but i think it has some very nice features that any distributed caching enthusiast would like. It also has a free version called NCache Express. Although this product is in .net domain but it works well with java too.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taylor Gautier</title>
		<link>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-438</link>
		<dc:creator>Taylor Gautier</dc:creator>
		<pubDate>Wed, 28 Jan 2009 02:57:46 +0000</pubDate>
		<guid>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-438</guid>
		<description>@Rik,

I wouldn't think so.   You can get more details on the licensing here:

http://www.terracotta.org/web/display/docs/FAQ#FAQ-LicensingFacts

But in essence, unless you are redistributing Terracotta - e.g. you make an application that relies on Terracotta, you bundle that application up and then sell it, you are now redistributing.</description>
		<content:encoded><![CDATA[<p>@Rik,</p>
<p>I wouldn&#8217;t think so.   You can get more details on the licensing here:</p>
<p><a href="http://www.terracotta.org/web/display/docs/FAQ#FAQ-LicensingFacts" rel="nofollow">http://www.terracotta.org/web/display/docs/FAQ#FAQ-LicensingFacts</a></p>
<p>But in essence, unless you are redistributing Terracotta - e.g. you make an application that relies on Terracotta, you bundle that application up and then sell it, you are now redistributing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: znachor</title>
		<link>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-431</link>
		<dc:creator>znachor</dc:creator>
		<pubDate>Tue, 20 Jan 2009 18:11:56 +0000</pubDate>
		<guid>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-431</guid>
		<description>Mahesh, following the locality of reference paradigm you would still prefer to handle requests regarding particular entity on a given set of node to minimize distributed locking when Terracotta delivers up-to-date version of that object. You can achieve the effect of partitioning by appropriate request routing to cluster nodes so that the necessary object will always be found on that local server and therefore synchronization overhead between terracotta server and cluster nodes minimized.</description>
		<content:encoded><![CDATA[<p>Mahesh, following the locality of reference paradigm you would still prefer to handle requests regarding particular entity on a given set of node to minimize distributed locking when Terracotta delivers up-to-date version of that object. You can achieve the effect of partitioning by appropriate request routing to cluster nodes so that the necessary object will always be found on that local server and therefore synchronization overhead between terracotta server and cluster nodes minimized.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mahesh Venkat</title>
		<link>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-426</link>
		<dc:creator>Mahesh Venkat</dc:creator>
		<pubDate>Sun, 18 Jan 2009 20:52:45 +0000</pubDate>
		<guid>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-426</guid>
		<description>Hi, 
With respect to work load partitioning,  why do we still need layer 7 sticky session Loadbalancer configuration for user sessions.
It is expensive to route http requests within a user's session to any node of a cluster?

Thanks
--Mahesh</description>
		<content:encoded><![CDATA[<p>Hi,<br />
With respect to work load partitioning,  why do we still need layer 7 sticky session Loadbalancer configuration for user sessions.<br />
It is expensive to route http requests within a user&#8217;s session to any node of a cluster?</p>
<p>Thanks<br />
&#8211;Mahesh</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Rik</title>
		<link>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-327</link>
		<dc:creator>Rik</dc:creator>
		<pubDate>Sat, 20 Dec 2008 01:59:17 +0000</pubDate>
		<guid>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-327</guid>
		<description>Hi Taylor,

would applications that use SMS to communicate with endusers need to provide attribution? If yes, where? Its not feasible to include it in each SMS, given the limited capacity of an SMS.</description>
		<content:encoded><![CDATA[<p>Hi Taylor,</p>
<p>would applications that use SMS to communicate with endusers need to provide attribution? If yes, where? Its not feasible to include it in each SMS, given the limited capacity of an SMS.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Taylor Gautier</title>
		<link>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-296</link>
		<dc:creator>Taylor Gautier</dc:creator>
		<pubDate>Thu, 04 Dec 2008 22:31:09 +0000</pubDate>
		<guid>http://www.woloszyn.org/2008/12/04/evaluating-terracotta/#comment-296</guid>
		<description>Hi Piotr.

Really great write-up.  Wow!  

One minor correction, the Terracotta license requires attribution (adding "Powered by Terracotta") only for users that are re-distributing.  Normal uses of Terracotta would not require this restriction.

More info is available on our licensing page: http://www.terracotta.org/web/display/orgsite/Licensing

Once again, impressive summary of all of our available information.

Regards, 

Taylor Gautier
Product Manager, Terracotta</description>
		<content:encoded><![CDATA[<p>Hi Piotr.</p>
<p>Really great write-up.  Wow!  </p>
<p>One minor correction, the Terracotta license requires attribution (adding &#8220;Powered by Terracotta&#8221;) only for users that are re-distributing.  Normal uses of Terracotta would not require this restriction.</p>
<p>More info is available on our licensing page: <a href="http://www.terracotta.org/web/display/orgsite/Licensing" rel="nofollow">http://www.terracotta.org/web/display/orgsite/Licensing</a></p>
<p>Once again, impressive summary of all of our available information.</p>
<p>Regards, </p>
<p>Taylor Gautier<br />
Product Manager, Terracotta</p>
]]></content:encoded>
	</item>
</channel>
</rss>
