Hi Cees,
> If I miss the part in the docs where it tells me to do that, I may get
> frustrated with the module, because it "does not work as advertised". I
> shouldn't have to alter any code that has nothing to do with Authentication
> just
> to use this module.
Agreed. Given the example, it makes sense to me that C::App defaults to
"automatic" forwarding.
> Thats true, but that could be done with a subclass and overriding the method.
> for example, lets use the authentication module example again. If I use
> CGI::App::Auth and I want to capture the cgiapp_prerun method it uses and do
> my
> own thing instead, then I create a subclass of CGI::App::Auth and override
> it's
> cgiapp_runmode method and use the subclass in my modules instead.
This sounds like a reasonable way to override default behavior.
> Hope that answers your questions.
Yes, thanks, it does; unfortunately the docs you pointed me to are a bit
outside my current scope of understanding. Perhaps your reimplementation
in C::App will help.
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).
Regards,
William
--
Knowmad Services Inc.
http://www.knowmad.com
---------------------------------------------------------------------
Web Archive: http://www.mail-archive.com/cgiapp@xxxxxxxxxxxxxxxxx/
http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: cgiapp-unsubscribe@xxxxxxxxxxxxxxxxx
For additional commands, e-mail: cgiapp-help@xxxxxxxxxxxxxxxxx
|
