Re^2: CGI::Application in a team development environment

[cees]

My experiences with CGIApp are very much in line with what perrin's is stating. If you break up your runmode modules into logical tasks, you will end up with a whole bunch of modules with only about 3 or 4 runmodes in each. If you start noticing that you have 10 - 15 runmodes, then perhaps you should think of break this into smaller pieces.

One thing that some users find annoying about breaking the application up into smaller pieces like this is that you require a small CGI script for each of your runmode modules to fire up the application. We have found that using the CGI::Application::Dispatch module really simplifies this by having a single CGI script (or mod_perl handler) that can spawn multiple runmode modules based on the PATH_INFO of the request.

Also, I find that most of the logic in any of the larger CGI::Apps I have built tends to fall into the Model of the application. Most of the runmodes tend to be quite simple and generally just pass data between the Model and the View, with a bit of data validation thrown in.