Comments on: Learning Rails: Namespaced Controllers http://www.claytonlz.com/2008/05/learning-rails-namespaced-controllers/ Agile Practitioner, CSP, CSPO, CSM in Phoenix, AZ Sat, 05 Nov 2011 10:33:16 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: Anurag http://www.claytonlz.com/2008/05/learning-rails-namespaced-controllers/#comment-3 Anurag Sat, 06 Feb 2010 09:03:11 +0000 http://www.claytonlz.com/?p=8#comment-3 Couldn't agree more with this article. I am deciding between a separate namespaced admin vs a pure roles based solution like declarative_authorization and certainly a namespaced approach sounds much better to me for two reasons. First, an admin's workflow is not necessarily similar to how a normal user would use the application. So there'd be separate view and controllers those those workflows. Don't think that counts as duplication. Secondly, management is easier. Everything under the namespace /admin has to be protected by all means. There is no need to worry about modifying views if user is this/that, etc. That said, I think a perfect solution would be to have both namespaced admin area for the application admins, and a role based approach for all other kinds of users. Couldn’t agree more with this article. I am deciding between a separate namespaced admin vs a pure roles based solution like declarative_authorization and certainly a namespaced approach sounds much better to me for two reasons. First, an admin’s workflow is not necessarily similar to how a normal user would use the application. So there’d be separate view and controllers those those workflows. Don’t think that counts as duplication. Secondly, management is easier. Everything under the namespace /admin has to be protected by all means. There is no need to worry about modifying views if user is this/that, etc.

That said, I think a perfect solution would be to have both namespaced admin area for the application admins, and a role based approach for all other kinds of users.

]]> By: Guillaume http://www.claytonlz.com/2008/05/learning-rails-namespaced-controllers/#comment-2 Guillaume Wed, 06 May 2009 15:30:35 +0000 http://www.claytonlz.com/?p=8#comment-2 Well, it's been a while since you wrote this, but I'm now facing exactly the same problem ('Portin out a PHP CMS into Rails). Excepting I don't understand you : "two controllers, two views, two stylesheets..." Well, isn't that the way it MUST be ?! I mean, in a CMS, your back do have many features and views that your front does not handle, no ?! It appears to me total and "absolute" split of the two sides is necessary (and what about themes, for instance ?...) Your post surprised me, is there something I totally miss ? About the namespacing of the controllers, well, it is clearly not a solution without consequences, but -in my opinion- it is the only clean, powerful, and proper solution. ... But as I always say : I maybe wrong ;-) Well, it’s been a while since you wrote this, but I’m now facing exactly the same problem (‘Portin out a PHP CMS into Rails). Excepting I don’t understand you : “two controllers, two views, two stylesheets…” Well, isn’t that the way it MUST be ?! I mean, in a CMS, your back do have many features and views that your front does not handle, no ?! It appears to me total and “absolute” split of the two sides is necessary (and what about themes, for instance ?…)
Your post surprised me, is there something I totally miss ?
About the namespacing of the controllers, well, it is clearly not a solution without consequences, but in my opinion it is the only clean, powerful, and proper solution.

… But as I always say : I maybe wrong ;-)

]]>