Comments on: When to use Nested Controllers in your Rails apps http://www.sentia.com.au/2009/09/when-to-use-nested-controllers-in-your-rails-apps/ Sentia company website and blog about all things development, Ruby on Rails, Microsoft .Net, ASP.Net, C#.Net, Agile web development, Test Driven Development Wed, 11 Jan 2012 14:17:22 +0000 hourly 1 http://wordpress.org/?v=3.2.1 By: Michael Cindric http://www.sentia.com.au/2009/09/when-to-use-nested-controllers-in-your-rails-apps/comment-page-1/#comment-208 Michael Cindric Wed, 25 Nov 2009 21:27:45 +0000 http://sentia.com.au/?p=575#comment-208 Thats right you still have the one model as the model is the interaction with the DB. You can create another model can set it to speak with the same tables but better to have just the one model and 2 controllers as the controllers handle the interaction for the users Thats right you still have the one model as the model is the interaction with the DB. You can create another model can set it to speak with the same tables but better to have just the one model and 2 controllers as the controllers handle the interaction for the users

]]> By: Joe http://www.sentia.com.au/2009/09/when-to-use-nested-controllers-in-your-rails-apps/comment-page-1/#comment-206 Joe Wed, 25 Nov 2009 12:17:10 +0000 http://sentia.com.au/?p=575#comment-206 I like it! Something is still missing for me though. This technique separates admin_user code from front end user code. So this means we have one model, and two controllers: a normal scaffolded user (not mentioned above) and the admin bits you describe above? I like it! Something is still missing for me though. This technique separates admin_user code from front end user code.

So this means we have one model, and two controllers: a normal scaffolded user (not mentioned above) and the admin bits you describe above?

]]>