I think the concept is an idea which will appeal to lazy developers.
Why on earth would you want to put conditionals into your code that you
know will only evaluate to a set value in the environment they run in?
If anything it makes problems harder to track down because if someone
takes a
I think this is an over-simplification of a complex problem. Here are
a few examples from orbitz.com:
- Thread pool sizes. We couldn't replicate production (1500+ servers)
in staging, so instead, we created as many VMs as we could handle on
the limited number of machines we had (~100) to
Dear Apache Struts 2 team,
Some friends and I are working on a PHP5 M.V.C. framework with an
interface that could look like the one of Struts 2 (the XML configuration
file - the DTD in fact).
The engine will be soon available as an opensource project, but we would
like to know if you are ok if
Brian,
From what I can see your only real problem is QA on config files and
given that how can you you can guarentee that all of your servers will
never have their config drifted between zones because a certain problem
occurr in dev but does in production.
I've previously worked on a
--- On Sat, 6/28/08, Tom951 [EMAIL PROTECTED] wrote:
Please keep us posted if that's ok for you - it would be huge.
It's open source-absorb what is useful.
Dave
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
I'm not sure what you see as lazy, exactly?
Frank
-Original Message-
From: Al Sutton [EMAIL PROTECTED]
Sent: Saturday, June 28, 2008 12:06 PM
To: Struts Developers List dev@struts.apache.org
Subject: Re: environment awareness (project stage in JSF)
Brian,
From what I can see your only
Wow. This got way off topic, but I'm compelled to answer. ;)
Your assumption about QA being the only problem is incorrect. It is
environment based. The application should not be changed in anyway
when it is migrated across boundaries. It should be able to determine
where it is and how it
Isn't it a bit ironic that a programmer would call automation lazy?
(*Chris*)
On Sat, Jun 28, 2008 at 12:15 PM, Frank W. Zammetti [EMAIL PROTECTED] wrote:
I'm not sure what you see as lazy, exactly?
Frank
-Original Message-
From: Al Sutton [EMAIL PROTECTED]
Sent: Saturday, June
--- On Sat, 6/28/08, Brian Pontarelli wrote:
[Applications should not have to change migrating across boundaries.]
+1
I am fundamentally lazy. IMO it's worth the (potentially substantial) up-front
costs to remove environment-specific application code wherever possible: it's
more expensive
Hi Dave,
Thanks for your quick answer.
But I'm sorry, I did not understand what you said (sorry I'm not american :)
!).
Could you explain?
Thanks a lot,
Thomas
newton.dave wrote:
--- On Sat, 6/28/08, Tom951 [EMAIL PROTECTED] wrote:
Please keep us posted if that's ok for you - it would be
On Sat, Jun 28, 2008 at 10:40 PM, Tom951 [EMAIL PROTECTED] wrote:
Hi Dave,
Thanks for your quick answer.
But I'm sorry, I did not understand what you said (sorry I'm not american :)
!).
Could you explain?
What he means is that Struts is an open source project; you're free to
model your
Ok great. So you told me that it is ok to reuse your DTD? That's huge !!
Thanks a lot,
Thomas
Philip Luppens wrote:
On Sat, Jun 28, 2008 at 10:40 PM, Tom951 [EMAIL PROTECTED] wrote:
Hi Dave,
Thanks for your quick answer.
But I'm sorry, I did not understand what you said (sorry I'm not
--- On Sat, 6/28/08, Tom951 [EMAIL PROTECTED] wrote:
So you told me that it is ok to reuse your DTD?
Just follow the Apache license guidelines if you're using actual
files/artifacts/materials/etc. (i.e., leave the header in place, etc.)
I'm not sure what the rules are, if any, for derivative
On Sat, Jun 28, 2008 at 12:29 PM, Brian Pontarelli [EMAIL PROTECTED] wrote:
Your assumption about QA being the only problem is incorrect. It is
environment based. The application should not be changed in anyway when it
is migrated across boundaries. It should be able to determine where it is
14 matches
Mail list logo
