in reply to Re: designing a dispatch class
in thread designing a dispatch class

looking at the article briefly, it's a little too featureless. i'll need to take a closer look at it and see if i can use it to instantiate objects ...

ultimately, i need to do something like:

my $foo; $foo = MyModule::ActionSet1->new() if ( condition ); $foo = MyModule::ActionSet2->new() if ( condition2 ); $foo->process(); print $foo->output();
there are enough actions that even a hash-based dispatch table would get ugly.

it could split into a set of CGI::Application-based classes, which is perfect for CGI::Application::Dispatch-based applications. but i'm not sure that's the direction i *should* be going.

Replies are listed 'Best First'.
Re^3: designing a dispatch class
by tlm (Prior) on Mar 30, 2005 at 23:35 UTC

    I found the slide show more illuminating than the article; start with that. Take a look at the activate method (there's a slide on it about 2/3 of the way through the presentation), which neatly summarizes the module's logic.

    the lowliest monk