> > OTOH, maybe you're interested in a "MVC" -- > Model-View-Controller design, > with Perl modules which contain high-level functionality. If > this is your > goal, then I think I may have an important clarification for you: > CGI::Application is the "Controller" -- *NOT* the "Model". > > I tend to design using a MVC strategy, using CGI-App. My App > modules use > many other Perl modules which implement business logic. The > Controller (my > App module) provides the interface glue between the Model > modules (business > logic) and the web browser. Essentially, it converts form input into > function calls, and raw data into HTML::Template input. > (HTML::Template is > the View part -- data into HTML.) > >
Exactly! But what I don't quite understand is why the "Controller" has to generate output each and every time? When converting form input into function calls, wouldn't it be nice to use the controller to "Control" some branching without generating spurious output. Eventually some output will be needed, but not until the form has been properly processed. In fact, depending on data in the form, wouldn't it be nice to be able to choose which HTML::Template pattern to use? Elizabeth Vaughn --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
