[Catalyst] New Root Controller in Catalyst 5.66

[Matt S Trout]

On Wed, Mar 01, 2006 at 06:00:01AM +0100, Sebastian Riedel wrote:
> 
> 01.03.2006 05:39 Nilson Santos Figueiredo Junior:
> 
> > On 3/1/06, Sebastian Riedel <sri at oook.de> wrote:
> >> This is another best practice promoted to be part of core, it will
> >> eliminate namespace collisions like for the famous "login" action in
> >> combination with auth plugins. ;)
> >
> > This change is great for those who started using Catalyst.
> > I got somewhat frustrated when I spent something like half an hour (or
> > more) trying to figure out what was wrong with my application only to
> > then think about that "login" action. I now feel glad to know it's a
> > common mistake and you're trying to encourage best practices against
> > it.
> >
> > I just wonder. With the advent of YAML configuration files and this
> > Root controller, the base application class will be pretty much empty,
> > right? Or is there something else people usually put in there?
> 
> Right, it gets "cleaner". :)
> The application class was from the beginning just meant as a place to  
> interact with Catalyst "internals", load plugins, configure the app  
> and the like.

And of course, your $c for each request is blessed into that class by
default (unless you set __PACkAGE__->context_class to something else).

-- 
     Matt S Trout       Offering custom development, consultancy and support
  Technical Director    contracts for Catalyst, DBIx::Class and BAST. Contact
Shadowcat Systems Ltd.  mst (at) shadowcatsystems.co.uk for more information

 + Help us build a better perl ORM: http://dbix-class.shadowcatsystems.co.uk/ +