<?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>Commentaires sur : Fragmented Java or no Java ?</title>
	<atom:link href="http://blog.appliweb.net/2009/06/fragmented-java-or-no-java/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.appliweb.net/2009/06/fragmented-java-or-no-java/</link>
	<description>All dimensions of your web developments</description>
	<lastBuildDate>Fri, 03 Sep 2010 08:36:12 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>Par : John Smith</title>
		<link>http://blog.appliweb.net/2009/06/fragmented-java-or-no-java/comment-page-1/#comment-127</link>
		<dc:creator>John Smith</dc:creator>
		<pubDate>Tue, 16 Feb 2010 12:24:01 +0000</pubDate>
		<guid isPermaLink="false">http://blog.appliweb.net/?p=73#comment-127</guid>
		<description>The good thing about your fragmented platform that is Java based is that it will not gain enough marketshare where it will matter that you need to test on all platforms.  The low number of users on each device will mean that it won&#039;t be cost effective.</description>
		<content:encoded><![CDATA[<p>The good thing about your fragmented platform that is Java based is that it will not gain enough marketshare where it will matter that you need to test on all platforms.  The low number of users on each device will mean that it won&#8217;t be cost effective.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
