The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

So, the entire app would only have 2 controllers? If this isn't the case, can you provide me with an example as I don't have a copy of the book... yet.

You can subclass your controllers too, so you can for example have a Products controller in both the admin and client sections. For example, these two commands will create product controllers, one for public use and one for admins*:

So, the entire app would only have 2 controllers? If this isn't the case, can you provide me with an example as I don't have a copy of the book... yet.

No. Use as many controllers as you need but you will generally need more than two otherwise you would probably end up with massive controllers which is poor design. Controllers should be like any other class, with only as many methods as needed, and focussed on a particular subject.

The best option is to take advantage of Rails' built-in routing for Ruby modules.

Create a folder in your controller folder called "admin". Then, for all controllers inside this folder, make them part of an Admin module, so you might have a user controller for both the admin and front end: