Any update on this? We're about to upgrade to T5.3, but conveniently use template reload in production on rare occasions. >From prior discussions a symbol would/could be introduced, but don't seem like it has..?
Any way of supporting reload(without production=false)? Or is the dynamic component the way to go? Not a showstopper - just want to know what my options are... thanks Magnus On Fri, Apr 22, 2011 at 9:01 PM, Vangel V. Ajanovski <a...@ii.edu.mk> wrote: > On 20.04.2011 21:03, Thiago H. de Paula Figueiredo 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. :) > > I would like to know what is truly the nature of the problem with live > reload (besides possibility to get the application in an inconsistent > state of which every developer is aware). > > What is the range of the performance penalty? 0.01%, 1%, 5%, 20%, ... is > it raising exponentially on the number of all pages? Memory use? Permgen > filling too quickly? > Is it really only about performance, or does it have other problems too? > What other (under the hood) differences do production and development > modes have? > > Howard started this discussion without really explaining the reasons for > not having it at all or even the reasons for not having an option that > would enable it in production. > >
