David Zülke kirjoitti:
My thoughts exactly. Either my clients are dumb or don't care, and let me do
the stuff, or they are smart and fumble around with their system. If the
latter is the case, they can just as well install Phing. I really find the
concept very, very appealing.
You have to think about "clients" little more widely. I consider all
users - both developers and end users that use some application
developed on top of Agavi - our "clients". Let's take for example some
killer forum (killer as in killer application, not a forum for killers)
web application (isn't web forums what PHP is designed anyway :) The
application must work almost-out-off-to-box. Debug cannot be on but
requiring Phing just to get some other application installed would
definitely be an overkill. This could of course be solved by setting
debug on, running once and then setting debug back to false... but, like
bob said, this is kludgy. So the way Agavi cache now works would suit
perfectly.
I think having an Phing task to build cache file and disabling mod time
checks is a Great idea, but we must not take away the current
options/behaviour. And again, TTL-setting should be taken into a
consideration now too (even if we decide to implement it later or not at
all).
-veikko
P.S. I promised David that my branch is ready for merging this saturday
night (GMT). The merging, however, is going to be nasty because there
are so many conflicts. I'm going to need help with it as I have never
done it before.
_______________________________________________
agavi-dev mailing list
[email protected]
http://labworkz.com/cgi-bin/mailman/listinfo/agavi-dev
