I'm always looking for ways to streamline Tapestry on the server. One thing that, I believe, is over-engineered is the available set of render phases, aka, the component render state machine.
http://tapestry.apache.org/component-rendering.html (I remember designing this current state machine while on a flight somewhere). >From what I can tell, BeforeRenderTemplate, BeforeRenderBody, AfterRenderTemplate, and AfterRenderBody are not used anywhere inside the framework, outside of tests. I believe they can be safely removed from the framework, along with the support for the naming convention methods. At the very least, I'd like to deprecate them in 5.4 and entirely remove them in 5.5. Currently Tapestry optimizes the render phases for each component based on which render phases have a method. Removing support for these four render phases would reduce the construction cost of components, and reduce the amount of garbage generated when constructing a page. I believe we could also optimize the render phases even more tightly, reducing the number of render phase operations needed to render a page. In the aggregate, this might amount to a perceptible difference in performance or memory utilization. I'd like to hear from anyone in the overall community that relies on the any of these annotations. -- Howard M. Lewis Ship Creator of Apache Tapestry The source for Tapestry training, mentoring and support. Contact me to learn how I can get you up and productive in Tapestry fast! (971) 678-5210 http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
