please don't blame me if I'm wrong here. just point it out and I'll
apologize :-)
the first is to load all modules at beginning. I want to ask why? for
$c-forward()? I think $c-model() can load when called. why I hate this
is because it eats too many memory. one of my App has 80+ pm then it
On Thursday 03 January 2008 10:51:47 Fayland Lam wrote:
please don't blame me if I'm wrong here. just point it out and I'll
apologize :-)
the first is to load all modules at beginning. I want to ask why? for
$c-forward()? I think $c-model() can load when called. why I hate this
is because it
Fayland Lam wrote:
the first is to load all modules at beginning. I want to ask why? for
$c-forward()? I think $c-model() can load when called. why I hate this
is because it eats too many memory. one of my App has 80+ pm then it
takes 150+M. I can't afford that!
You don't mention how you are
Simon
Catalyst is a web application framework. You have two choices:
1. Use a simple LWP type script in cron to call the necessary web URI
and let the server do the heavy lifting; or
2. Make sure you encapsulate the business logic in the model and not in
the controller, then you can just load
A normal mistake of managing web servers these days is to put
tons of web
applications onto one server and letting them fight over resources.
Servers
(and memory in particular) is a low cost factor (compared to
development
costs). Then why not give your lovely web application some GB's of
On Thu, 3 Jan 2008, Peter Edwards wrote:
In the latter case there's still some work to do if you want to have a
shared config file but that's not too hard to figure out.
There's a Catalyst advent calendar article showing how to do this:
http://catalyst.perl.org/calendar/2007/14
I did
