<?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: WWW Required</title>
	<atom:link href="http://nslog.com/2005/10/31/www_required/feed" rel="self" type="application/rss+xml" />
	<link>http://nslog.com/2005/10/31/www_required</link>
	<description>The Weblog of Erik J. Barzeski</description>
	<pubDate>Sat, 22 Nov 2008 19:18:38 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.3</generator>
		<item>
		<title>By: Neil D'Souza</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17277</link>
		<dc:creator>Neil D'Souza</dc:creator>
		<pubDate>Wed, 02 Nov 2005 07:07:55 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17277</guid>
		<description>You can even set this up at your registrar... register.com allows this.
</description>
		<content:encoded><![CDATA[<p>You can even set this up at your registrar... register.com allows this.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tienshiao Ma</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17276</link>
		<dc:creator>Tienshiao Ma</dc:creator>
		<pubDate>Tue, 01 Nov 2005 01:57:18 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17276</guid>
		<description>I can understand the viewpoints of the "no-www" crowd, but I personally prefer the explicitness of the www.

Another reason why it may be preferred by some sites is that if you make use of a Content Delivery Network (such as Akamai), the standard practice is to make your site (www. or whatever) a CNAME of an Akamai hostname. If you wanted to put the domain on Akamai (instead of a subdomain) you would need to use Akamai as your nameserver (since you can't CNAME the domain). This is obviously less flexible than running your own nameservers.</description>
		<content:encoded><![CDATA[<p>I can understand the viewpoints of the "no-www" crowd, but I personally prefer the explicitness of the <a href="http://www" >http://www</a>.</p>
<p>Another reason why it may be preferred by some sites is that if you make use of a Content Delivery Network (such as Akamai), the standard practice is to make your site (www. or whatever) a CNAME of an Akamai hostname. If you wanted to put the domain on Akamai (instead of a subdomain) you would need to use Akamai as your nameserver (since you can't CNAME the domain). This is obviously less flexible than running your own nameservers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Simone Manganelli</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17275</link>
		<dc:creator>Simone Manganelli</dc:creator>
		<pubDate>Mon, 31 Oct 2005 17:49:38 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17275</guid>
		<description>Ugh, yes, I hate this so very much too.  And worst of all, my university ( http://stanford.edu/ oh whoops sorry http://www.stanford.edu/ ) has this problem.  I have to remember to e-mail someone about that to get it changed...

-- Simone</description>
		<content:encoded><![CDATA[<p>Ugh, yes, I hate this so very much too.  And worst of all, my university ( <a href="http://stanford.edu/" rel="nofollow">http://stanford.edu/</a> oh whoops sorry <a href="http://www.stanford.edu/" >http://www.stanford.edu/</a> ) has this problem.  I have to remember to e-mail someone about that to get it changed...</p>
<p>-- Simone</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Adam</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17274</link>
		<dc:creator>Adam</dc:creator>
		<pubDate>Mon, 31 Oct 2005 17:03:48 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17274</guid>
		<description>On my domain names, I used to have www.blah.tld work identically to blah.tld; but I decided that I shouldn't be defining two separate locatable URIs for every resource (and they are technically two separate URIs, even if they look almost the same), so instead, I now set www.blah.tld to redirect to blah.tld. That's working well.

Here's a good site dealing with this sensitive issue: http://no-www.org/ . They do it the same way as I do, redirecting www.no-www.org to no-www.org.</description>
		<content:encoded><![CDATA[<p>On my domain names, I used to have <a href="http://www.blah.tld" rel="nofollow">http://www.blah.tld</a> work identically to blah.tld; but I decided that I shouldn't be defining two separate locatable URIs for every resource (and they are technically two separate URIs, even if they look almost the same), so instead, I now set <a href="http://www.blah.tld" >http://www.blah.tld</a> to redirect to blah.tld. That's working well.</p>
<p>Here's a good site dealing with this sensitive issue: <a href="http://no-www.org/" rel="nofollow">http://no-www.org/</a> . They do it the same way as I do, redirecting <a href="http://www.no-www.org" >http://www.no-www.org</a> to no-www.org.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Daniel</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17273</link>
		<dc:creator>Daniel</dc:creator>
		<pubDate>Mon, 31 Oct 2005 14:40:57 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17273</guid>
		<description>I don't really care about that so much, but two related things that annoy me are:
- spoken URLs (like on TV) don't work.  Example: while the TV shows "www.today.msnbc.com," Katie &#38; Matt only actually say "today.msnbc.com."  Many times, the actual spoken URL does not work - the implied www is required.  How stupid.
- static URLs that don't end in a slash.  I've relaxed on this one a lot, but I still prefer nice clean URLs that go to directories with an index file, instead of directly to a file.</description>
		<content:encoded><![CDATA[<p>I don't really care about that so much, but two related things that annoy me are:<br />
- spoken URLs (like on TV) don't work.  Example: while the TV shows "www.today.msnbc.com," Katie &amp; Matt only actually say "today.msnbc.com."  Many times, the actual spoken URL does not work - the implied www is required.  How stupid.<br />
- static URLs that don't end in a slash.  I've relaxed on this one a lot, but I still prefer nice clean URLs that go to directories with an index file, instead of directly to a file.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Olivier</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17272</link>
		<dc:creator>Olivier</dc:creator>
		<pubDate>Mon, 31 Oct 2005 13:21:10 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17272</guid>
		<description>Some hosting providers have their home page appear for any domain accessed without the www. That's close to domain hijacking, I don't understand how they customenrs let them get away with it.</description>
		<content:encoded><![CDATA[<p>Some hosting providers have their home page appear for any domain accessed without the <a href="http://www" >http://www</a>. That's close to domain hijacking, I don't understand how they customenrs let them get away with it.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frode Danielsen</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17271</link>
		<dc:creator>Frode Danielsen</dc:creator>
		<pubDate>Mon, 31 Oct 2005 13:16:38 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17271</guid>
		<description>Heh, noticed just now that I commented on this the last time as well. Yeah, it must be quite a pet-peeve of mine too! The second comment on your last post on the topic was also a good read again.</description>
		<content:encoded><![CDATA[<p>Heh, noticed just now that I commented on this the last time as well. Yeah, it must be quite a pet-peeve of mine too! The second comment on your last post on the topic was also a good read again.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Frode Danielsen</title>
		<link>http://nslog.com/2005/10/31/www_required#comment-17270</link>
		<dc:creator>Frode Danielsen</dc:creator>
		<pubDate>Mon, 31 Oct 2005 13:10:49 +0000</pubDate>
		<guid isPermaLink="false">http://nslog.com/2005/10/31/www_required/#comment-17270</guid>
		<description>Agreed. I don't understand the hosts that don't get this right. I experience it quite often with .no TLDs. My dad, providing hosting services, have been making the case of the unnecessary "www" for a long time :-)</description>
		<content:encoded><![CDATA[<p>Agreed. I don't understand the hosts that don't get this right. I experience it quite often with .no TLDs. My dad, providing hosting services, have been making the case of the unnecessary "www" for a long time <img src='http://nslog.com/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
</channel>
</rss>
