David Zülke wrote:
OK.. so this assumes that you've run your app with the flag off at
least once (to get agavi to compile the config caches), and then turn
the flag off. Hmm.. It just seems kludgy to me. Now if we had a
phing task which would create the config caches (not even sure if
that's possible.. I haven't had my coffee yet), I would buy this in a
heartbeat. Whaddya think?
Proposal: I back this DONT_COMPILE_TEH_CONFIGS_YOU_RETARD flag out, and we
add such a functionality together with the phing task in 0.11. I could also
imagine this: with AG_DEBUG set to off, config checks aren't performed,
nothing is compiled etc, and you'd have to call the task manually. I think
this is even better, isn't it? In production environments, configs change
almost never, so it would be fine to do it this way.
Briefly a few things I talked about with David last night:
- Requiring Phing in production enviroment is not good.
- Requiring (likely a low-tech) customer/client to run building tasks is
not good.
So:
- I'm in favor of keeping the current behaviour (debug=on/off) and only
adding more choices (cache time-to-live and/or cache "freezing").
-veikko
_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
