No, I don''t think adding actions to the application controller is the
way to handle public requests. If that were the case, what would be
the point of being able to create controllers at all, other than
separating an admin section? As your site gets more complex, the
controller would just get huge, and eventually be responsible for much
more functionality than is manageable.
The easiest thing to do, in my mind, is logically separate your
controllers and then use routes to set the application entry point.
For example, if you''re writing a blog, you might have a BlogController
and use routes so that http://yoursite.com looks to
BlogController#index.
Pat
On 12/1/05, Rodrigo Alvarez Fernández
<papipo-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
wrote:> I have an application that has
> app/controllers/admin/*some_controllers_here*/
> Is it recommended to use the application controller as the main route to
> public requests? If not, i can create a new "index" controller or
something,
> buty i think that is not a good name. Which names do you usually use for
the
> main entry point (controller) in the application?
>
> Thanks,
> Rodrigo.
>
> _______________________________________________
> Rails mailing list
> Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org
> http://lists.rubyonrails.org/mailman/listinfo/rails
>
>
>