On Thu, 23 Sep 2004 12:28:29 -0400, William McKee <[EMAIL PROTECTED]> wrote: > On Thu, Sep 23, 2004 at 02:31:18PM +0000, Mark Stosberg wrote: > > - I wonder if the REALLY_FIRST, FIRST... position system could be > > simplified/improved. The way I think about it, either want you > > plug-in to run at one of three times at a particular stage: > > > > - before everything else > > - after everything else > > - you don't care. > > I agree with Mark. However, I'm wondering what it means to run > before/after "everything else". At what point in the CGI::App pipeline > would these hooks come into play? Over time, I'm guessing they would > displace the current cgiapp_init, cgiapp_prerun, cgiapp_teardown phases. > Since we have at least 3 points at which we can introduce additional > code, it seems that we would need at least 4 positions in the pipeline > (or do you plan to merge cgiapp_init with cgiapp_prerun in the > pipeline?). Perhaps we need to draw out the current pipeline (sorry if > I missed that step in previous discussions). > > I like Mark's suggestion of using an array to control order of > operation.
Has anyone thought of using Class::Trigger to handle the cgiapp_* hooks? Class::DBI uses this module for it's triggers. The downside is that it doesn't (currently) support running triggers is a particular order. I imagine that it could be added if someone had the need. I haven't thought much through the implications of this change, but once you get over the API changes it could make it much easier to add additional code that runs at each hook. Drew -- ---------------------------------------------------------------- Drew Taylor * Web development & consulting Email: [EMAIL PROTECTED] * Site implementation & hosting Web : www.drewtaylor.com * perl/mod_perl/DBI/mysql/postgres ---------------------------------------------------------------- --------------------------------------------------------------------- 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]
