It sounds like what your patch will ultimately provide is a way to easily add/remove functions into C::App which would make things much easier for new users as well as for those of us who have our favored modules and gobs of code to make them easily available in C::App (e.g., CGI::Session which you've made into an easily imported class saving me from dragging around my custom code from project to project).
That is exactly what I hope to achieve (actually, I should say 'we' cause I'm not the only one to share this view).
The great thing about CGI::Application is that it gives you the freedom to use whatever modules you want and buildup your own toolbox of code. But that is also a drawback to new users, since there is quite a bit of work that needs to be done if you want session support, authentication, logging, database access, etc...
By building a bunch of simple add on modules like the Session module I wrote, we can simplify life for newcomers, without restricting the power and flexibility that CGI::Application currently enjoys. And perhaps show long time users of CGI::Application other ways of handling these common (and sometimes mundane) tasks.
I currently have a Template Toolkit plugin that I have used in a couple of projects already, and also, an authentication plugin. However, for my authentication stuff to work, I need to be able to execute a bit of code at the cgiapp_prerun stage, which drove me to write this patch.
Perhaps what would help is if I rewrote that authentication module to actually use the features of the patch, and then provide both as a working example of what can be done.
Cheers,
Cees
--------------------------------------------------------------------- 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]
