On 2004-09-23, 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).
What meant I was "everything else" at each /stage/, where the stages are
currently:
cgiapp_init
cgiapp_prerun
cgiapp_postrun
teardown
So you might something to run before everything else in the 'prerun' stage,
or after everything else in 'teardown', for example.
I don't see this concept replacing the current phases we have, though.
It's not /that/ radical of change.
WWW::Pipeline has already published as a fully pipeline-centric
alternative.
Mark
--
. . . . . . . . . . . . . . . . . . . . . . . . . . .
Mark Stosberg Principal Developer
[EMAIL PROTECTED] Summersault, LLC
765-939-9301 ext 202 database driven websites
. . . . . http://www.summersault.com/ . . . . . . . .
---------------------------------------------------------------------
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]
