<?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: Vodafone Mobile Web (User-Agent) Debacle</title>
	<atom:link href="http://weblog.cenriqueortiz.com/mobileweb/2007/09/21/vodafone-mobile-web-user-agent-debacle/feed/" rel="self" type="application/rss+xml" />
	<link>http://weblog.cenriqueortiz.com/mobileweb/2007/09/21/vodafone-mobile-web-user-agent-debacle/</link>
	<description>CEO on Mobile &#38; Wireless</description>
	<lastBuildDate>Tue, 07 Sep 2010 16:57:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0.1</generator>
	<item>
		<title>By: GadgetGadget.info - Gadgets on the web &#187; Vodafone Mobile Web (User-Agent) Debacle</title>
		<link>http://weblog.cenriqueortiz.com/mobileweb/2007/09/21/vodafone-mobile-web-user-agent-debacle/comment-page-1/#comment-1848</link>
		<dc:creator>GadgetGadget.info - Gadgets on the web &#187; Vodafone Mobile Web (User-Agent) Debacle</dc:creator>
		<pubDate>Fri, 21 Sep 2007 22:36:11 +0000</pubDate>
		<guid isPermaLink="false">http://weblog.cenriqueortiz.com/mobileweb/2007/09/21/vodafone-mobile-web-user-agent-debacle/#comment-1848</guid>
		<description>[...] unknown wrote an interesting post today!.Here&#8217;s a quick excerptProviding a better mobile web user experience is about properly identifying the web client (typically via the User-Agent header), with the goal of properly serving content to the connecting device (based on its features/characteristics) &#8230; [...]</description>
		<content:encoded><![CDATA[<p>[...] unknown wrote an interesting post today!.Here&#8217;s a quick excerptProviding a better mobile web user experience is about properly identifying the web client (typically via the User-Agent header), with the goal of properly serving content to the connecting device (based on its features/characteristics) &#8230; [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>
