Hi!
Tapestry 5's live class reloading is a huge productivity boost, specially
when compared to almost any other web framework out there. Maybe 90% of
all web app reloads are eliminated.
But there is the remaining 10% of the reloads. Most of them are related to
new pages and components. In other words: Tapestry does not pick new
pages, components and templates after it is started. If this fact is
reversed, we could develop an entire web interface without reloading the
application.
In addition, there is one other reason to implement this new feature:
applications with static content. Every time I add a new page to my
website, www.arsmachina.com.br, I have to restart the application, as it's
written on T5. This is not an issue to arsmachina.com.br, but can be to
high traffic websites.
What do you think about this? I've just created it:
https://issues.apache.org/jira/browse/TAP5-315 If you agree with me,
please vote. :)
PS: My website does not have any interactivity, any logic yet. Just static
content. My website is implemented with T5, so I can use the Layout
component pattern and not repeat the pages' common parts (header, footer,
menu) on every page. T5 can be very useful even in static websites. :)
--
Thiago H. de Paula Figueiredo
Independent Java consultant, developer, and instructor
http://www.arsmachina.com.br/thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
