<?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: Java Takes A Step Forward With The SE P990i</title>
	<atom:link href="http://www.psynixis.com/blog/2005/10/11/java-takes-a-step-forward-with-the-se-p990/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.psynixis.com/blog/2005/10/11/java-takes-a-step-forward-with-the-se-p990/</link>
	<description>Simon Brocklehurst's Technology Blog</description>
	<pubDate>Tue, 06 Jan 2009 21:40:04 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: simon</title>
		<link>http://www.psynixis.com/blog/2005/10/11/java-takes-a-step-forward-with-the-se-p990/comment-page-1/#comment-205</link>
		<dc:creator>simon</dc:creator>
		<pubDate>Thu, 22 Dec 2005 15:11:43 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/?p=15#comment-205</guid>
		<description>In general, hardware/OS platforms on phones are not yet as stable as we have come to expect  with PCs.  However, it's really important to understand what "Enterprise Application" means in the context of mobile phone software.  Expectations that businesses have for software running on mobile phones are rather different than the expecations they have, say, for their server infrastructure.

The Java ME platform is currently more than adequate for developing software for the Enterprise; and it's only getting more powerful over time with business-focussed APIs e.g. for software manageability, security etc. being introduced.

Having said all that - the devil *is* in the detail.  If it turns out that SE have poor implementations of these APIs, then (by definition) they will not be usable for serious applications.</description>
		<content:encoded><![CDATA[<p>In general, hardware/OS platforms on phones are not yet as stable as we have come to expect  with PCs.  However, it&#8217;s really important to understand what &#8220;Enterprise Application&#8221; means in the context of mobile phone software.  Expectations that businesses have for software running on mobile phones are rather different than the expecations they have, say, for their server infrastructure.</p>
<p>The Java ME platform is currently more than adequate for developing software for the Enterprise; and it&#8217;s only getting more powerful over time with business-focussed APIs e.g. for software manageability, security etc. being introduced.</p>
<p>Having said all that - the devil *is* in the detail.  If it turns out that SE have poor implementations of these APIs, then (by definition) they will not be usable for serious applications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: jianwu</title>
		<link>http://www.psynixis.com/blog/2005/10/11/java-takes-a-step-forward-with-the-se-p990/comment-page-1/#comment-204</link>
		<dc:creator>jianwu</dc:creator>
		<pubDate>Thu, 22 Dec 2005 10:01:47 +0000</pubDate>
		<guid isPermaLink="false">http://www.psynixis.com/blog/?p=15#comment-204</guid>
		<description>J2ME on the phone for personal usage might be for developing game,
then a lot of new features might just mean wasting battery power.
J2ME on the phone for Enterprise Application requires more than 
device itself, reliability, connectivity, often a lot of new features might 
mean not reliable at all, considering all these new features are actually
software</description>
		<content:encoded><![CDATA[<p>J2ME on the phone for personal usage might be for developing game,<br />
then a lot of new features might just mean wasting battery power.<br />
J2ME on the phone for Enterprise Application requires more than<br />
device itself, reliability, connectivity, often a lot of new features might<br />
mean not reliable at all, considering all these new features are actually<br />
software</p>
]]></content:encoded>
	</item>
</channel>
</rss>
