# Default controller in RESTful Rails application

**URL:** <https://www.ruby-forum.com/t/default-controller-in-restful-rails-application/115427>\
**Category:** Rails\
**Created:** [September 25, 2007, 7:27am UTC](https://www.ruby-forum.com/t/default-controller-in-restful-rails-application/115427 "2007-09-25T07:27:15Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Martin\_Henriksson](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/b487fb/32.png) [@Martin\_Henriksson](https://www.ruby-forum.com/u/Martin_Henriksson)\
**Post date:** [September 25, 2007, 7:27am UTC](https://www.ruby-forum.com/t/default-controller-in-restful-rails-application/115427/1 "2007-09-25T07:27:15Z")

</div>

Hi!

Anyone have any tips for naming relations in a restful way?

My biggest problem using the RESTful approach is coming up with all  
controller names for relations that basically are verbs converted to  
substantives which sometimes gets pretty ugly. When you read tutorials  
they always present you with easy names for relations like “Newspapers  
-\> Subscriptions -\> Users” and “Groups -\> Memberships -\> Users”. But  
my lack of fantasy makes it hard.  
For instance; If I would like to have a relation between Groups and  
Users I would name it Membership. But if I in the same application  
would like the have the same type of relation between Groups and  
Groups I can’t use Membership again and have to figure out another  
“great” name that basically says the same thing. Because polymorphic  
relations lack true support for has\_many :through I cant use that  
successfully either.

It would be cool to have a long list of really good names for  
different controllers like Memberships, Subscriptions. Anyone sitting  
on such a list? 🙂