Hi Chris -- > im both new to CGI::Application and perl programming in general, > so bear with me... :) > My question isn't to do with the actual CGI::Application module > (which works just fine), but the wrapper cgi that kicks it all off.
By "wrapper cgi" are you talking about what the CGI::Application documentation calls the "instance script"? I've never heard your term before. > Currently i am messing around with a single cgi wrapper that > initializes one of a series of modules (instead of each one > having its own wrapper) based on the incoming querystring - kind > of like a traffic cop at a junction. > But it strikes me, that the wrapper cgi could possibly be used > for a lot more than this, and wondered how veterans like > yourselves use it, if at all. What you're describing is the way things *used* to be, before CGI::Application came along. The CGI::Application module was invented to get away from that type of architecture. IMHO, the instance script (what I think you are calling the "wrapper cgi"), should not contain any application logic. Putting application logic there simply moves code from your module to somewhere else. It doesn't make anything more simple -- just more spread out. And having code all over the place may actually make your architecture MORE complicated -- not less so. TTYL, -Jesse- --------------------------------------------------------------------- Web Archive: http://www.mail-archive.com/cgiapp@lists.vm.com/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
