<?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: Browsers vs. native apps: Vic Gundotra&#8217;s comments &#8211; Ecosystems, HTML5 and Long tail  ..</title>
	<atom:link href="http://www.opengardensblog.futuretext.com/archives/2009/07/browsers_vs_nat.html/feed" rel="self" type="application/rss+xml" />
	<link>http://www.opengardensblog.futuretext.com/archives/2009/07/browsers_vs_nat.html</link>
	<description>Wireless mobility - Innovation - Digital convergence - mobile web 2.0</description>
	<lastBuildDate>Thu, 19 Jan 2012 13:47:14 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Peter Cranstone</title>
		<link>http://www.opengardensblog.futuretext.com/archives/2009/07/browsers_vs_nat.html/comment-page-1#comment-1857</link>
		<dc:creator>Peter Cranstone</dc:creator>
		<pubDate>Tue, 18 Aug 2009 22:30:32 +0000</pubDate>
		<guid isPermaLink="false">http://dev5.indigocontenthost.co.uk/archives/2009/07/browsers_vs_nat.html#comment-1857</guid>
		<description>Device discovery is quite straightforward. You simply have the device transmit the information as part of the HTTP request being made to the web server.
HTML 5 has some advantages but is not fully supported on all the mobile browsers and is certainly not backwards compatible with existing mobile browsers.
There are free solutions out there that solve this problem and will support HTML5.
BTW Vic is correct - the future is mobile web apps in the browser. The sticky question is how.
</description>
		<content:encoded><![CDATA[<p>Device discovery is quite straightforward. You simply have the device transmit the information as part of the HTTP request being made to the web server.<br />
HTML 5 has some advantages but is not fully supported on all the mobile browsers and is certainly not backwards compatible with existing mobile browsers.<br />
There are free solutions out there that solve this problem and will support HTML5.<br />
BTW Vic is correct &#8211; the future is mobile web apps in the browser. The sticky question is how.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
<!-- WP Super Cache is installed but broken. The path to wp-cache-phase1.php in wp-content/advanced-cache.php must be fixed! -->
