P is for Practical | |
PerlMonks |
Re: Structuring multiple CGI::Application modulesby MrCromeDome (Deacon) |
on Jun 25, 2004 at 20:55 UTC ( [id://369750]=note: print w/replies, xml ) | Need Help?? |
I haven't been using C::A for too terribly long, but so far, it's been a blessing to my web development efforts ;) Your approach to this is not too dissimilar to my own: My applications have a lot in common, from configuration files to session parameters to application parameters. Typically, when one of my apps needs to handle a login, they simply redirect to my user module as follows: Notice the login_redirect param. Login uses this to decide where to send the user upon a successful login. My login handling code then looks like this: Some of these functions are from my own application code, but you should get the gist of what is going on. Sorry that I am unable to answer your question with regards to bloat. I'm not the best at profiling an application :( Hope this helps you somewhat and answers your questions. Feel free to bombard me with your questions.
Good luck!
In Section
Seekers of Perl Wisdom
|
|