Splitting resources or not

I have a resource named ‘users’ and another one ‘posts’, but these one
can have ‘offers’ or ‘requests’…

shouild I define 2 other resources or keep only one, using something
like :

map.resources :users, :collection => { :offer => :get }
map.resources :users, :collection => { :request => :get }

which will give me helper methods like :

offer_users_url #=> “/users;offer”
request_users_url #=> “/users;request”

and adding my own prefix to the generated url name:

map.resources :users, :collection => { :offer => :get }, :name_prefix =>
‘my_’
map.resources :users, :collection => { :request => :get }, :name_prefix
=> ‘my_’

giving
my_offer_users_url #=> “/users;offer”
my_offer_users_url #=> “/users;offer”

what is the best design ? one or 2 resources …

On May 14, 2:09 am, Kad K. [email protected]
wrote:

I have a resource named ‘users’ and another one ‘posts’, but these one
can have ‘offers’ or ‘requests’…

Can you explain this just a bit more? What are these “offers” and
“requests”, and how are they represented in your model associations?

Jeff

This forum is not affiliated to the Ruby language, Ruby on Rails framework, nor any Ruby applications discussed here.

| Privacy Policy | Terms of Service | Remote Ruby Jobs