Hi, I''ve read this great article about how a REST application can be organized (http://scottraymond.net/) - The author also refactored his admin (backoffice) actions. But I wonder how it is possible to have admin and user actions in the same controllers without encountering situations where the meaning of actions have both senses. For example : /products/new is admin only - So no problem here but /products/index generate a list of products on the web site and generate a list of products for the admin (where the format and the tools provided have nothing in common with the web site list) So, one ''list'' action must have another name and this break the REST way of thinking... What is the solution in that case ? Still put admin action in admin only controllers ? Create admin only actions like admin_list ? I really don''t see what to do - Thanks -- Posted via http://www.ruby-forum.com/. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---