It would be great to reduce this "turnaround time".
Indeed, for the developpers, it's really painful, even with the "no cache" option on. For sure, I don't know the internal of the beast, but from a (low level ;)) developper point of view, the turnaround time is pretty important, and the slower the better ! Thanks in advance ZedroS On 7/20/06, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Haven't had the tools and opportunity to tell, but seems a lot slower on startup and first-time page load, and perceptibly faster at execution (as long as caching is enabled). On 7/20/06, Skriloff, Nicholas <[EMAIL PROTECTED]> wrote: > How much faster have you found tapestry 4 to be over tapestry 3? > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Jakarta HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- 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]
