It looks like you have some sort of event-driven architecture. My first instinct is to use callbacks. Something like:

my %callbacks = (
    foo => \&do_foo,
    bar => \&do_bar,
etc ...
);

my $action = $cgi->param('action');

my $callback = $callbacks{$action};

die "No callback!\n" unless $callback;

return $callback->(@args);
[download]

Then, you work some neat mechanism of registering the callbacks. They can even be the result of can (but you have to have an appropriate object to call it on) or method names (to be called on appropriate objects, presumably with can).

Of course, using CGI::Application is good cause it encapsulates the annoying work for you. :-)

------
We are the carpenters and bricklayers of the Information Age.

Don't go borrowing trouble. For programmers, this means Worry only about what you need to implement.

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.