<?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: Live from TSS-JS &#8211; Mobile Development with Mark	</title>
	<atom:link href="https://www.selikoff.net/2011/03/16/live-from-tss-js-mobile-development-with-mark/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.selikoff.net/2011/03/16/live-from-tss-js-mobile-development-with-mark/</link>
	<description>Java/J2EE Software Development and Technology Discussion Blog</description>
	<lastBuildDate>Thu, 17 Mar 2011 07:15:02 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.9.4</generator>
	<item>
		<title>
		By: Ulf		</title>
		<link>https://www.selikoff.net/2011/03/16/live-from-tss-js-mobile-development-with-mark/comment-page-1/#comment-3603</link>

		<dc:creator><![CDATA[Ulf]]></dc:creator>
		<pubDate>Thu, 17 Mar 2011 07:15:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=2906#comment-3603</guid>

					<description><![CDATA[True, the API is a bit hobbled by having to be general enough to accommodate non-DB data sources in ContentProvider (which is also a plus, on the other hand). But it is rather different than JDBC.

I don&#039;t agree with the &quot;not common&quot; comment on JME, by the way. I&#039;m pretty sure there are more JME phones being used than all of iOS/Android/WinMobile/WP 7 etc. combined. They&#039;re not smartphones, though; maybe that got lost during transcription. And the BlackBerry *does* run on JME, but has additional BB-specific APIs.]]></description>
			<content:encoded><![CDATA[<p>True, the API is a bit hobbled by having to be general enough to accommodate non-DB data sources in ContentProvider (which is also a plus, on the other hand). But it is rather different than JDBC.</p>
<p>I don&#8217;t agree with the &#8220;not common&#8221; comment on JME, by the way. I&#8217;m pretty sure there are more JME phones being used than all of iOS/Android/WinMobile/WP 7 etc. combined. They&#8217;re not smartphones, though; maybe that got lost during transcription. And the BlackBerry *does* run on JME, but has additional BB-specific APIs.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Mark		</title>
		<link>https://www.selikoff.net/2011/03/16/live-from-tss-js-mobile-development-with-mark/comment-page-1/#comment-3600</link>

		<dc:creator><![CDATA[Mark]]></dc:creator>
		<pubDate>Wed, 16 Mar 2011 22:59:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=2906#comment-3600</guid>

					<description><![CDATA[What I meant by that statement is the API is cludgy and awkward to use.]]></description>
			<content:encoded><![CDATA[<p>What I meant by that statement is the API is cludgy and awkward to use.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Ulf		</title>
		<link>https://www.selikoff.net/2011/03/16/live-from-tss-js-mobile-development-with-mark/comment-page-1/#comment-3598</link>

		<dc:creator><![CDATA[Ulf]]></dc:creator>
		<pubDate>Wed, 16 Mar 2011 22:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.selikoff.net/?p=2906#comment-3598</guid>

					<description><![CDATA[&quot;Android requires a lot of manual work to integrate with a database, such as SQL Lite, whereas Apple iOS has this built in.&quot; - Something&#039;s amiss here. Android has SQLite built in, and an API to use it. No &quot;integration&quot; needs to be done, and certainly nothing manual.]]></description>
			<content:encoded><![CDATA[<p>&#8220;Android requires a lot of manual work to integrate with a database, such as SQL Lite, whereas Apple iOS has this built in.&#8221; &#8211; Something&#8217;s amiss here. Android has SQLite built in, and an API to use it. No &#8220;integration&#8221; needs to be done, and certainly nothing manual.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
