Comments on: Restful Routing: An Overview

By: Pan

Pan — Tue, 05 Aug 2008 22:52:56 +0000

Thanks for writing such a helpful article.
I’ve learned really much from it.

By: Brenton

Brenton — Tue, 17 Jun 2008 01:25:45 +0000

Very funny post! If only I’d found this when I was learning REST.

By: Radar

Radar — Fri, 23 May 2008 12:41:15 +0000

The Restful routing syntax is designed to be easier to use, and yes of course it’s not going to be compatible with previous versions of Rails (what is? :)). The reason why I prefer to use it is, instead of typing link_to “New Blog”, :controller => “blogs”, :action => “new” I can now type < %= link_to "New Blog", new_blog_path %>, or even < %= link_to "New Blog", @blog %> if @blog is defined as Blog.new.

Yes, it will be a pain bringing those older views in line with the new syntax but once you’ve done it you get a consistent, easy to use syntax across everything.

How were you specifying variables in your redirect_to before?

By: Gudasoft » Blog Archive » Rails 2.0 scaffolding

Gudasoft » Blog Archive » Rails 2.0 scaffolding — Fri, 23 May 2008 12:25:51 +0000

[…] http://frozenplague.net/2008/01/06/restful-routing-an-overview/ […]

By: Hadmut

Hadmut — Thu, 22 May 2008 20:33:44 +0000

Hi,

sorry to contradict, but restful routing is neither plain nor simple. In my eyes it is just bad design.

If it were plain and simple, it would not require such explanatory articles.

I am just busy with porting a rails application to rails 2.0 and found that this restful routing breaks backwards compatiblity. Old views don’t work with new views generated with scaffolding. Formerly the paths were of the simple structure /:controller/:action/:id, but now they don’t have any consistent structure anymore.

Formerly, functions like redirect_to could take variables as parameters for controller, action and id, but now I don’t see a way to do this consistently anymore.

In my eyes, the restful routing is of poor design and shortsighted. It just causes confusion and makes things more complicated.

Was there any good reason to introduce it?

By: Tom

Tom — Tue, 15 Apr 2008 22:18:18 +0000

Good post!

Worthwhile as well: http://api.rubyonrails.com/classes/ActionController/Resources.html

Interestingly, your post seems to be more advanced in some points than the API description…

By: zeroeth

zeroeth — Thu, 10 Apr 2008 03:16:51 +0000

Hey Radar!

Great post about nested resources. I see lots of people asking and I only ever have one link to show them, this makes two =)

By: The Life Of A Radar » Blog Archive » Administration Namespacing

The Life Of A Radar » Blog Archive » Administration Namespacing — Sun, 16 Mar 2008 00:50:00 +0000

[…] so I figured if I sat down and wrote this, I would have something to send to people, much like my Restful Routes tutorial, which ideally should’ve covered namespacing […]

By: Jose Espinal

Jose Espinal — Fri, 07 Mar 2008 05:17:38 +0000

Great great article! You don’t know how grateful I am for it, explained a lot of holes I had about REST.

By: debianfreak

debianfreak — Sun, 17 Feb 2008 14:55:22 +0000

Ok… I figured it out. I needed to use link_to ‘Messages’, person_messages_path(@person) and then it works I didn’t see that mentioned… perhaps you should add it?

Great article though - it helped me a lot!