Re^3: Structuring multiple CGI::Application modules II

The redirect can also be external. Just issue a 302 to the appropriate controller CGI script. Remember - C::A is just a fancy way of handling multiple requests in the same CGI script. If you read the rest of my replies in Why CGI::Application?, you'll see that I had some 4-5 different CGI scripts, each handling a different type of content, with a master script handling login functionality. So, do something like:

Go to the login runmode.
User enters credentials.
The validate function does "The Right Thing"(tm). (Probably determined by a CGI parameter.)
It then issues a 302 to the appropriate content-handling CGI script. This would be determined by a CGI parameter.

------
We are the carpenters and bricklayers of the Information Age.

Then there are Damian modules.... *sigh* ... that's not about being less-lazy -- that's about being on some really good drugs -- you know, there is no spoon. - flyingmoose

I shouldn't have to say this, but any code, unless otherwise stated, is untested

Comment on Re^3: Structuring multiple CGI::Application modules II


Clear questions and runnable code get the best and fastest answer
	PerlMonks