The vote to release Tapestry version 5.0.15 is under way. This is the release candidate. Once it's available, we'll give it a few weeks of exposure (while I'm in Europe) and then, barring any unforeseen critical bugs, we will vote it up as the 5.0 GA release.
I already have extensive plans for improvements to Tapestry in 5.1. I want one of the compelling reasons to use Tapestry to be performance, so I'm looking at automatically GZIPing content, compressing JavaScript (and perhaps combining JavaScript files together), making increased use of far-future expired headers and so forth. In other words, just make the framework do the right thing.
I think there's also room to optimize the server-side further. I have some ideas for limiting the number of render commands needed to render a page, and limit the amount of work wasted on event notifications that have no listener.
5 comments:
"so I'm looking at automatically GZIPing content, compressing JavaScript (and perhaps combining JavaScript files together), making increased use of far-future expired headers and so forth. In other words, just make the framework do the right thing."
+1. I was looking for that from a framework for a while now.
BR,
~A
Isn't gzipping the content more a task for the server (eg. apache's mod_deflate)? Anyway, it should be optional.
Enabling compression on application level allows more control over what gets compressed and what not. Also not everybody is using apache frontend.
what about portlet support? are there any plans for portlet support in tapestry 5?
auto gzip/js compression would be cool :-)
And 5.1 will be the first test of backwards compatibility which was always Tapestry's worst weakness...
Post a Comment