<?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: No index.php</title>
	<atom:link href="http://gondwanaland.com/mlog/2008/05/20/no-indexphp/feed/" rel="self" type="application/rss+xml" />
	<link>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/</link>
	<description>My opinions only. I do not represent any organization in this publication.</description>
	<pubDate>Mon, 13 Oct 2008 02:29:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.2</generator>
		<item>
		<title>By: Lucas</title>
		<link>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/#comment-99392</link>
		<dc:creator>Lucas</dc:creator>
		<pubDate>Tue, 29 Jul 2008 17:16:52 +0000</pubDate>
		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=531#comment-99392</guid>
		<description>In spoken language the 'www'  is a better cue than 'h-t-t-p'.  

Yahoo misses all those little signs of craftsmanship pretty often.  I spent months attempting to get GUIDs out the URLs.

The yimg URLs go to akamai or y's internal caching network.</description>
		<content:encoded><![CDATA[<p>In spoken language the &#8216;www&#8217;  is a better cue than &#8216;h-t-t-p&#8217;.  </p>
<p>Yahoo misses all those little signs of craftsmanship pretty often.  I spent months attempting to get GUIDs out the URLs.</p>
<p>The yimg URLs go to akamai or y&#8217;s internal caching network.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crosbie Fitch</title>
		<link>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/#comment-98934</link>
		<dc:creator>Crosbie Fitch</dc:creator>
		<pubDate>Wed, 21 May 2008 09:30:46 +0000</pubDate>
		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=531#comment-98934</guid>
		<description>'www' could have been selected to cue the speaker to greater precision in their speech and the listener to greater concentration in correctly interpreting the following identifier. A sort of line conditioner like the ten pulses of the zero that starts all telephone numbers (well, it worked like that once).

It also serves as a good audio marker for any speech analysis software.

Ok, so TBL just thought it looked cute - and then made up some lame excuse about it being memorable and standing for 'world wide web'.</description>
		<content:encoded><![CDATA[<p>&#8216;www&#8217; could have been selected to cue the speaker to greater precision in their speech and the listener to greater concentration in correctly interpreting the following identifier. A sort of line conditioner like the ten pulses of the zero that starts all telephone numbers (well, it worked like that once).</p>
<p>It also serves as a good audio marker for any speech analysis software.</p>
<p>Ok, so TBL just thought it looked cute - and then made up some lame excuse about it being memorable and standing for &#8216;world wide web&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mike Linksvayer</title>
		<link>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/#comment-98932</link>
		<dc:creator>Mike Linksvayer</dc:creator>
		<pubDate>Tue, 20 May 2008 23:08:56 +0000</pubDate>
		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=531#comment-98932</guid>
		<description>Good point re caching.  It seems that Yahoo takes the domainstatic.com approach -- yimg.com -- though yahoo.com redirects to www.yahoo.com.

I do like meaningful subdomains where appropriate.</description>
		<content:encoded><![CDATA[<p>Good point re caching.  It seems that Yahoo takes the domainstatic.com approach &#8212; yimg.com &#8212; though yahoo.com redirects to <a href="http://www.yahoo.com" rel="nofollow">http://www.yahoo.com</a>.</p>
<p>I do like meaningful subdomains where appropriate.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Mohr</title>
		<link>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/#comment-98929</link>
		<dc:creator>Gordon Mohr</dc:creator>
		<pubDate>Tue, 20 May 2008 21:49:05 +0000</pubDate>
		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=531#comment-98929</guid>
		<description>Also: for a site that has (or may have) different language versions, the wikipedia per-language subdomain approach is nice. It offers a subdomain on which to hang the login cookie -- such as en.wikipedia.org -- that's more meaningful than 'www.'.</description>
		<content:encoded><![CDATA[<p>Also: for a site that has (or may have) different language versions, the wikipedia per-language subdomain approach is nice. It offers a subdomain on which to hang the login cookie &#8212; such as en.wikipedia.org &#8212; that&#8217;s more meaningful than &#8216;www.&#8217;.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gordon Mohr</title>
		<link>http://gondwanaland.com/mlog/2008/05/20/no-indexphp/#comment-98928</link>
		<dc:creator>Gordon Mohr</dc:creator>
		<pubDate>Tue, 20 May 2008 21:44:45 +0000</pubDate>
		<guid isPermaLink="false">http://gondwanaland.com/mlog/?p=531#comment-98928</guid>
		<description>I was long in the no-www camp. 

But then via the Yahoo 'Best Practices for Speeding Up Your Web Site', I was reminded that if your site's cookies are set on domain.com, they will be sent to every subdomain.domain.com, too. That presents problems for caching, even if you segment all static resources off to a 'static.domain.com' subdomain. 

Solution: either set up a different owned domain like domainstatic.com for cacheable resources, or embrace the 'www.' and set your application cookies only on 'www.domain.com'. 

So the www is not all bad. 

See: http://developer.yahoo.com/performance/rules.html#cookie_free

(Point taken about index.php, of course. Clean URLs are one of the dozens of little things that send a signal of craftsmanship to a savvy audience. Others that spring to mind: ALT/TITLEs for images; making radio/checkbox labels active; intuitive tab orders; layouts that work at different font sizes; form submits that redirect to non-POST reloadable pages.)</description>
		<content:encoded><![CDATA[<p>I was long in the no-www camp. </p>
<p>But then via the Yahoo &#8216;Best Practices for Speeding Up Your Web Site&#8217;, I was reminded that if your site&#8217;s cookies are set on domain.com, they will be sent to every subdomain.domain.com, too. That presents problems for caching, even if you segment all static resources off to a &#8217;static.domain.com&#8217; subdomain. </p>
<p>Solution: either set up a different owned domain like domainstatic.com for cacheable resources, or embrace the &#8216;www.&#8217; and set your application cookies only on &#8216;www.domain.com&#8217;. </p>
<p>So the www is not all bad. </p>
<p>See: <a href="http://developer.yahoo.com/performance/rules.html#cookie_free" rel="nofollow">http://developer.yahoo.com/performance/rules.html#cookie_free</a></p>
<p>(Point taken about index.php, of course. Clean URLs are one of the dozens of little things that send a signal of craftsmanship to a savvy audience. Others that spring to mind: ALT/TITLEs for images; making radio/checkbox labels active; intuitive tab orders; layouts that work at different font sizes; form submits that redirect to non-POST reloadable pages.)</p>
]]></content:encoded>
	</item>
</channel>
</rss>
