Hi,
In a busy live environment I would prefer disabled by default
but still doable programmatically for occasional critical patching.
This would allow reloading to be hooked for example to some
administrative web service and result in better atomicity if multiple
files need to be patched.
That said, I currently deploy entire app most of the times.
Cheers,
--Nikla
On 20.4.2011 22:43, Kalle Korhonen wrote:
On Wed, Apr 20, 2011 at 10:03 PM, Thiago H. de Paula Figueiredo
<thiag...@gmail.com> wrote:
On Wed, 20 Apr 2011 15:21:10 -0300, LLTYK<ll...@mailinator.com> wrote:
Disabled, so you automatically get better performance. I don't think you
should have to tweak Tapestry options to get better performance.
Good point. But a similar argument can be used: enabled, so you get a faster
development environment without tweaking options. My gosh, these decisions
are hard. :)
Everybody wants better performance but only certain group of users
want/need reloading in production. For the whole discussion -
personally I think live reloading is the wrong way to solve the
application upgrade / patching problem, you give up too much for the
benefit. I've been doing skinny wars, deploying dependent libs
separately and auto-reloading of the web app for a few years, to
achieve production deployment and updates in less than two seconds.
Together with Tomcat 7's parallel deployment, you get a nice zero
downtime environment.
Kalle
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and
instructor
Owner, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
