Re: Re: Re: Scaling single-script CGI applications

It sounds like we are largely in agreement. And I'm not the one " ...focusing on the idea of 'one module is the application' related to CGI::Application too much. "

From the Abstract of CGI::Application's documentation:

The guiding philosophy behind CGI::Application is that a web-based application can be organized into a specific set of ``Run-Modes.'' Each Run-Mode is roughly analogous to a single screen (a form, some output, etc.). All the Run-Modes are managed by a single ``Application Module'' which is a Perl module.

Since the subject of the node is "Scaling single-script CGI applications" (my emphasis) I thought it important to point out that the single-module approach is not the way to go. But we agree on that, right? :)

Comment on Re: Re: Re: Scaling single-script CGI applications

Replies are listed 'Best First'.
Re: Re: Re: Re: Scaling single-script CGI applications by Hero Zzyzzx (Curate) on Jul 09, 2001 at 07:08 UTC
Yes. Sorry I didn't articulate it very clearly, but what I was getting at is that you can create a central repository of shared stuff, and then split out your major functions into different modules, not a single script application. CGI::Application makes this very easy, and this functionality is very well thought out by the author, Jesse Erlbaum. If you were thinking of starting an application as a single script, with the idea that you may split it out later, CGI::Application would be a good way to start. When you were ready to split your single script app up, you'd put your setup() or cgi_appinit() subs into your shared SuperClass and your other modules could run pretty much untouched. This might be a good way to go: Develop with CGI::Application for all it provides for a single script app, AND because it'll set you up better down the road as you need to bump up your script's functionality.	[reply]

Replies are listed 'Best First'.

Re: Re: Re: Re: Scaling single-script CGI applications
by Hero Zzyzzx (Curate) on Jul 09, 2001 at 07:08 UTC

Yes. Sorry I didn't articulate it very clearly, but what I was getting at is that you can create a central repository of shared stuff, and then split out your major functions into different modules, not a single script application. CGI::Application makes this very easy, and this functionality is very well thought out by the author, Jesse Erlbaum.

If you were thinking of starting an application as a single script, with the idea that you may split it out later, CGI::Application would be a good way to start.

When you were ready to split your single script app up, you'd put your setup() or cgi_appinit() subs into your shared SuperClass and your other modules could run pretty much untouched.

This might be a good way to go: Develop with CGI::Application for all it provides for a single script app, AND because it'll set you up better down the road as you need to bump up your script's functionality.

[reply]