Jesse Erlbaum wrote: > > Hi Mark -- > > > > This, IMHO, is a good example of the M-V-C pattern, > > implemented using > > > CGI::Application. > > > > I like that division as well. However, your Controller modules could > > still grow large. Say you have 40 run modes in a module. At any given > > time, you are using 1 to 3 of them. > > What you need to do in this case is to strike a better balance between > run-modes and Application modules. If you have 40 run-modes in one > Application module but you only use about one to three of them "at any given > time", that would suggest to me that you should, instead, have about 40 / 3 > Application modules -- about 13 to 14 separate applications containing about > three run-modes each.
I see. So the design question here is: Which parts of my application are logically distinct? Then I could pull apart the pieces that are less interdependent. Using your theoretical design above, would you then have 13 instance scripts, one for each module? Or one instance script with some glue that selected the right module to use? I'd be interested in an example. Thanks, -mark http://mark.stosberg.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
