<?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"
	>
<channel>
	<title>Comments on: JSTM for GWT: An Interesting Solution for Object Replication and Synchronization</title>
	<atom:link href="http://www.pathf.com/blogs/2008/04/jstm-for-gwt-an/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.pathf.com/blogs/2008/04/jstm-for-gwt-an/</link>
	<description>Running commentary about agile development, user experience design and Ajax.</description>
	<pubDate>Fri, 21 Nov 2008 20:56:31 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Cyprien Noel</title>
		<link>http://www.pathf.com/blogs/2008/04/jstm-for-gwt-an/#comment-23</link>
		<dc:creator>Cyprien Noel</dc:creator>
		<pubDate>Mon, 21 Apr 2008 10:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=23#comment-23</guid>
		<description>&lt;p&gt;Hello, thank you and Didier for this post! XSTM can be used for object caching like memcacheD or Terracotta but its more specific feature is client/server replication. E.g. to write a .NET or GWT UI for a Java server. Compared to Terracotta, XSTM is very similar but it uses optimistic locking (transactions) instead of pessimistic (distributed locks) and lacks some of their features like virtual heap, persistence etc...&lt;/p&gt;

</description>
		<content:encoded><![CDATA[<p>Hello, thank you and Didier for this post! XSTM can be used for object caching like memcacheD or Terracotta but its more specific feature is client/server replication. E.g. to write a .NET or GWT UI for a Java server. Compared to Terracotta, XSTM is very similar but it uses optimistic locking (transactions) instead of pessimistic (distributed locks) and lacks some of their features like virtual heap, persistence etc&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Debasish Ghosh</title>
		<link>http://www.pathf.com/blogs/2008/04/jstm-for-gwt-an/#comment-22</link>
		<dc:creator>Debasish Ghosh</dc:creator>
		<pubDate>Mon, 21 Apr 2008 04:54:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.pathf.com/blogs/?p=23#comment-22</guid>
		<description>&lt;p&gt;How does solutions like XSTM stack up with memcacheD or Terracotta ? Do they address the same use cases ?&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>How does solutions like XSTM stack up with memcacheD or Terracotta ? Do they address the same use cases ?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
