[Jakarta-tapestry Wiki] Update of "Tapestry4" by HowardLewisShip

classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

[Jakarta-tapestry Wiki] Update of "Tapestry4" by HowardLewisShip

Apache Wiki
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Jakarta-tapestry Wiki" for change notification.

The following page has been changed by HowardLewisShip:
http://wiki.apache.org/jakarta-tapestry/Tapestry4

------------------------------------------------------------------------------
  ## page was renamed from Tapestry31
  #pragma section-numbers off
- = Tapestry 3.1 =
+ = Tapestry 4.0 =
 
  Work on Tapestry 3.0 has ''finally'' come to a close, and the focus is now on what comes next.
 
- Hopefully, Tapestry 3.1 will not drag on for as long as Tapestry 3.0 (a year and a half!).  More information is available on the Tapestry31Status page.
+ Hopefully, Tapestry 4.0 will not drag on for as long as Tapestry 3.0 (a year and a half!).  More information is available on the Tapestry31Status page.
+
+ ''Woops!  Guess it did!  -- Howard''
 
  Tapestry is now using HiveMind's build system ... heres notes on BuildingTapestry31.
 
@@ -55, +57 @@

 
  '''Update''': Yep, that's in there, and works great.
 
- = Offline Content Generation (3.2?) =
+ = Offline Content Generation (4.1?) =
 
  This has come up ... the idea of using Tapestry to generate ''static'' web pages. This is a technique used by many high-volume web sites ... much of the content is neither fully dynamic nor personalized. It changes at fixed intervals and might as well be a static web page that is auto-magically updated.
  An alternative is to use your preferred http server's error handling mechanism to ask your app server to generate the static page (when possible): if the page is here, ok the http server serves it, otherwise it redirects the request to your app server (which in turn saves the final response). If you want to update, delete the static files.
@@ -64, +66 @@

 
  = Portlet Support =
 
- Supporting porlets in Tapestry 3.1 is gaining an ever higher priority.
+ Supporting porlets in Tapestry 4.0 is gaining an ever higher priority.
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]