Re^2: In CGI::Application cgiapp_prerun vs. cgiapp

Thanks dragonchild, that helps. I assume by "persistent" you mean something like mod_perl? I'm running the regular old CGI cycle, so may I can just dispense with the cgiapp_prerun.

Well, on to C::A and cookies...

—Brad
"The important work of moving the world forward does not wait to be done by perfect men." George Eliot

Comment on Re^2: In CGI::Application cgiapp_prerun vs. cgiapp_init?

Replies are listed 'Best First'.
Re^3: In CGI::Application cgiapp_prerun vs. cgiapp_init? by dragonchild (Archbishop) on Dec 12, 2005 at 18:37 UTC
I can just dispense with the cgiapp_prerun. Don't. You will still benefit mentally from the separation of app-setup vs. response-setup. Plus, if you keep them separate, your migration to mod_perl will be easier when (not if!) it happens. My criteria for good software: Does it work? Can someone else come in, make a change, and be reasonably certain no bugs were introduced?	[reply]
Re^4: In CGI::Application cgiapp_prerun vs. cgiapp_init? by bradcathey (Prior) on Dec 12, 2005 at 19:30 UTC
Gotcha. Then, would you mind looking at my code and telling me then if I am using the two (prerun and init) properly. Thanks much —Brad "The important work of moving the world forward does not wait to be done by perfect men." George Eliot	[reply]
Re^3: In CGI::Application cgiapp_prerun vs. cgiapp_init? by trwww (Priest) on Dec 14, 2005 at 16:50 UTC
Cookies? What are cookies? http://cgiapp.erlbaum.net/cgi-bin/cgi-app/index.cgi?CgiApplicationPluginSessionExample :0)	[reply]


Just another Perl shrine
	PerlMonks

Re^2: In CGI::Application cgiapp_prerun vs. cgiapp_init?