<?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: Sexy URLs, or, Default Routes Considered Harmful</title>
	<atom:link href="http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/</link>
	<description>Just another WordPress weblog</description>
	<lastBuildDate>Tue, 09 Mar 2010 10:08:35 +0500</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.2</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Mark Wilden</title>
		<link>http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/comment-page-1/#comment-120</link>
		<dc:creator>Mark Wilden</dc:creator>
		<pubDate>Mon, 29 Sep 2008 17:13:51 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smarteguru.com/?p=288#comment-120</guid>
		<description>Yeah, we use GUIDs for ids in publically visible URLs.</description>
		<content:encoded><![CDATA[<p>Yeah, we use GUIDs for ids in publically visible URLs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rick</title>
		<link>http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/comment-page-1/#comment-118</link>
		<dc:creator>rick</dc:creator>
		<pubDate>Mon, 29 Sep 2008 07:18:40 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smarteguru.com/?p=288#comment-118</guid>
		<description>If you consider search engines to be users, sure.  Obviously if your pages are private, this doesn&#039;t mean a whole lot.  Saying &#039;Default Routes Considered Harmful&#039; is definitely a bit extreme.  This is just one more tool on the toolbelt.

One thing to keep in mind is you may not want users to be able to extrapolate the number of users or widgets in your system by looking at the sequential IDs.  Depending on your business, that may be potentially protected information.</description>
		<content:encoded><![CDATA[<p>If you consider search engines to be users, sure.  Obviously if your pages are private, this doesn&#8217;t mean a whole lot.  Saying &#8216;Default Routes Considered Harmful&#8217; is definitely a bit extreme.  This is just one more tool on the toolbelt.</p>
<p>One thing to keep in mind is you may not want users to be able to extrapolate the number of users or widgets in your system by looking at the sequential IDs.  Depending on your business, that may be potentially protected information.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mark Wilden</title>
		<link>http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/comment-page-1/#comment-114</link>
		<dc:creator>Mark Wilden</dc:creator>
		<pubDate>Fri, 26 Sep 2008 20:11:03 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smarteguru.com/?p=288#comment-114</guid>
		<description>I just don&#039;t get it. To me, a URL is something I click on or, at worst, copy and paste. I don&#039;t expect meaning, so I don&#039;t look for it. 

Do users really care about this?</description>
		<content:encoded><![CDATA[<p>I just don&#8217;t get it. To me, a URL is something I click on or, at worst, copy and paste. I don&#8217;t expect meaning, so I don&#8217;t look for it. </p>
<p>Do users really care about this?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rick</title>
		<link>http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/comment-page-1/#comment-110</link>
		<dc:creator>rick</dc:creator>
		<pubDate>Thu, 25 Sep 2008 18:52:25 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smarteguru.com/?p=288#comment-110</guid>
		<description>I&#039;d stay in the habit of using _id param names in routes: article/:category_id.  The category update action would use params[:category]  for the category options.  The param is still an identifier, even if isn&#039;t numerical.

Eric: permalink_fu won&#039;t reset your permalink (by default) for that very reason.  However, there&#039;s another couple reasons why your idea is preferred (IMO).  1) You can fetch by ID now by calling #to_i on the parameter.  Take advantage of the default pkey index.  2) Since the permalink doesn&#039;t matter, we don&#039;t care about unique permalinks anymore.  use `has_permalink :foo, :unique =&gt; false`.  It won&#039;t create unique permalinks like &#039;foo&#039;, &#039;foo-1&#039;, &#039;foo-2&#039; anymore.</description>
		<content:encoded><![CDATA[<p>I&#8217;d stay in the habit of using _id param names in routes: article/:category_id.  The category update action would use params[:category]  for the category options.  The param is still an identifier, even if isn&#8217;t numerical.</p>
<p>Eric: permalink_fu won&#8217;t reset your permalink (by default) for that very reason.  However, there&#8217;s another couple reasons why your idea is preferred (IMO).  1) You can fetch by ID now by calling #to_i on the parameter.  Take advantage of the default pkey index.  2) Since the permalink doesn&#8217;t matter, we don&#8217;t care about unique permalinks anymore.  use `has_permalink :foo, :unique =&gt; false`.  It won&#8217;t create unique permalinks like &#8216;foo&#8217;, &#8216;foo-1&#8242;, &#8216;foo-2&#8242; anymore.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Eric Anderson</title>
		<link>http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/comment-page-1/#comment-109</link>
		<dc:creator>Eric Anderson</dc:creator>
		<pubDate>Thu, 25 Sep 2008 13:33:00 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smarteguru.com/?p=288#comment-109</guid>
		<description>This works great of course until you rename your category. Now you got a bunch of broken links. The id should always be in the URL. Even if you have other information for the user. So:

/article/5-geography/13-european-capitals

Is a much better URL because you can do the find with the ID but still have something nice to look at in the URL. Since you are finding by the ID the name can change as it is just for the user. There are a few plugins that will do this automatically for you.</description>
		<content:encoded><![CDATA[<p>This works great of course until you rename your category. Now you got a bunch of broken links. The id should always be in the URL. Even if you have other information for the user. So:</p>
<p>/article/5-geography/13-european-capitals</p>
<p>Is a much better URL because you can do the find with the ID but still have something nice to look at in the URL. Since you are finding by the ID the name can change as it is just for the user. There are a few plugins that will do this automatically for you.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joshua</title>
		<link>http://blogs.smarteguru.com/ruby-on-rails/sexy-urls-or-default-routes-considered-harmful/comment-page-1/#comment-108</link>
		<dc:creator>Joshua</dc:creator>
		<pubDate>Thu, 25 Sep 2008 08:18:44 +0000</pubDate>
		<guid isPermaLink="false">http://blogs.smarteguru.com/?p=288#comment-108</guid>
		<description>Check out this routing plugin, it lets you do the same thing restfully
http://github.com/caring/default_routing/tree/master</description>
		<content:encoded><![CDATA[<p>Check out this routing plugin, it lets you do the same thing restfully<br />
<a href="http://github.com/caring/default_routing/tree/master" rel="nofollow">http://github.com/caring/default_routing/tree/master</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
