Re: [cgiapp] Re: register_hooks() proposal

[Clayton Scott <suppressed>]

Cees Hek wrote:

> So in the current system, we have 4 methods that act as hooks (cgiapp_init,
> cgiapp_prerun, cgiapp_postrun, teardown).  I think it might clear things up if
> we actually call the hooks like this (init prerun postrun teardown), and then
> refer to the default callbacks that are registered at those hooks as
> (cgiapp_init, cgiapp_prerun, cgiapp_postrun, teardown).
>
> So as an example, the cgiapp_prerun callback will automatically be registered at
> the prerun hook with the default ordering (DONTCARE).  
>  
So, these are like Class::Trigger triggers?


Clayton Scott

---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
             http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed