Spinning this off into a new thread. > So make it a controller base class. > > People make everything a plugin by default because it seems like a good idea > at the time. This has resulted in massive compatibility issues due to > namespace collisions. > > Don't Do It.
I've pondered the "controller vs. plugin" choice myself several times, and I see I'm not alone. I see the namespace issue with plugins, but does the potential for conflict make all plugins evil? This is another area where a clear best practices would be quite helpful. Matt, could you share your thoughts on when it's appropriate to choose a plugin over a base controller and vice versa? I'm guessing plugins become necessary when you need to get your hooks into a specific piece of Catalyst framework logic in order to achieve your goal -- like overriding and extending a method. Is a controller preferable in all other cases? Anybody else have thoughts on this? _______________________________________________ List: Catalyst@lists.rawmode.org Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/catalyst@lists.rawmode.org/ Dev site: http://dev.catalyst.perl.org/
