[cgiapp] Good practices: how many run modes in an app

[Brad Cathey <suppressed>]

I'm writing a medium-sized web-based financial application that will have up
to 50 run modes between presenting empty forms, saving, editing, updating,
and deleting from them. Run modes *could* be broken down into groups, e.g.,
these 4 deal with managing users, these 6 deal with managing project
specifications, etc.

Being new to C::A I'm curious if there are any general rules of thumb as to
the number of run modes (subs) that are run in any given Appl.pm. Besides
the long list under setup, there might be performance issues, and places
where trying to use a common sub might get messy.

In my pre-C::A days I would have been more inclined to break it down into
various scripts, maybe by function. But I'm not sure of how this fleshes out
in a C::A world.

Comments?

Thanks, Brad



---------------------------------------------------------------------
Web Archive:  http://www.mail-archive.com/suppressed/
              http://marc.theaimsgroup.com/?l=cgiapp&r=1&w=2
To unsubscribe, e-mail: suppressed
For additional commands, e-mail: suppressed