<?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"
	>
<channel>
	<title>Comments on: Step 1 - Choosing a Domain</title>
	<atom:link href="http://www.mobile-seo.co.uk/step-1-choosing-a-domain/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mobile-seo.co.uk/step-1-choosing-a-domain/</link>
	<description>No frills search engine optimisation: where simplicity works</description>
	<pubDate>Fri, 12 Mar 2010 11:36:03 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5</generator>
		<item>
		<title>By: Pelle Boese</title>
		<link>http://www.mobile-seo.co.uk/step-1-choosing-a-domain/#comment-13</link>
		<dc:creator>Pelle Boese</dc:creator>
		<pubDate>Wed, 02 Apr 2008 16:12:44 +0000</pubDate>
		<guid isPermaLink="false">#comment-13</guid>
		<description>Iam using both versions, 2 and 3. Whenever possible I host the mobile applications under the same domain with the same directory structure. For blogs etc this is pretty ease. For larger projects where we use Sevenval FIT to mobilize the site, we need a subdomain like m.domain.tld or wap.domain.tld because the mobile version is a completely different host. Anyways, I'd always prefer the "all-sites-under-one-domain" solution :)</description>
		<content:encoded><![CDATA[<p>Iam using both versions, 2 and 3. Whenever possible I host the mobile applications under the same domain with the same directory structure. For blogs etc this is pretty ease. For larger projects where we use Sevenval FIT to mobilize the site, we need a subdomain like m.domain.tld or wap.domain.tld because the mobile version is a completely different host. Anyways, I&#8217;d always prefer the &#8220;all-sites-under-one-domain&#8221; solution <img src='http://www.mobile-seo.co.uk/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /></p>
]]></content:encoded>
	</item>
</channel>
</rss>
