> Instead of trying to guess all the different plugin points a developer
> could want, we could implement a syntax by which the developer could
> make their own plugin calls. We could call it Perl!
Lol... I was about to write the same thing.
> Kidding aside, my favorite thing about CGI::Application is its
> simplicity. It's a simple module which gets its job done in a very
> small amount of code. Jesse used to say that CGI::App was more of a
> philosophy than a technology, and that suited me just fine. The pace
> of recent development makes me wonder how long that will remain true,
> if it still is.
At it's essence, the CGI::Application module must be able to do things
simply:
use base 'CGI::Application';
sub setup {...}
sub my_runmode {...}
If anyone wants to create a module which requires that you specify
plugins, or forces you to do anything more than declare and implement
run mode methods, then go and write your own framework. (May I
recommend you call it CGI::Application::Very::Simple::And::Lite? Heh..)
> Let's not try to make CGI::App into a plugin system for every
> web-development task. The world has enough of those already. Or, put
> another way, if what you really want is Catalyst then you know where
> to find it.
Thank you!
-Jesse-
--
Jesse Erlbaum
The Erlbaum Group
[EMAIL PROTECTED]
Phone: 212-684-6161
Fax: 212-684-6226
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/[email protected]/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
