Jesse Erlbaum wrote: > > Hi Mark -- > > > 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. > > I would have 13 separate instance scripts -- one for each application > module. The separate applications would be "connected" via HTTP requests.
Got it. I got myself in trouble once though trying to use this design, but organizing my modules by user role rather than the function of the module. Take for instance a search form that may be used by admins, editors and public users. If I'm using admin.cgi and public.cgi, and I need to create a link the second search page, linking either admin.cgi or public.cgi could be wrong, because the other kind of user could be using it. What makes more sense is to have a "Search.pm" module that would be used by both the Public and the Admins. -mark http://mark.stosberg.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
