Just to bring it round Dave, were talking about application logic whose
execution is based on an environment setting, so we're not talking about
a base dev-config.txt and production-config.txt, we're talking about an
application where something like a method will only return test data in
dev and qa, and only do the actual processing in production.
My point is that this is bad, if there is the choice to return test data
or do the processing it should be done in a config file alterable by the
deployer and not by the developer hard coding it into the code.
Dave Newton wrote:
--- On Sun, 6/29/08, Al Sutton <[EMAIL PROTECTED]> wrote:
And so don't you then come to the conclusion of what is
the point of a dev, test, prod switch when things are set
individually anyway?
*Can* be set individually; you bring up a special case, which would necessitate a special
case configuration. The application still wouldn't change, it doesn't mean that the
"base" configuration sets (D/T/P) are invalidated by particular need, nor that
a base config couldn't be used with a relatively minor tweak.
I've kind of lost track of the original point anyway :/ I'll still try to keep
my applications as isolated as possible from the environment they run in, and I
have yet to hear any alternatives. But no, I don't come to the conclusion that
base configurations are pointless.
Dave
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
