Inheritance is often over-used in the Java world. The performance impact is quite minimal, nothing to be concerned about. Further, there are optimizations that can be made within framework code to further improve performance (at some point I'll see if they are necessary but I honestly think they will not be).
Performance isn't an issue, but you ability to understand what your code does is impacted by having much (or even any) inheritance. Using aggregation rather than inheritance is usually the best approach. On 4/23/07, bjornharvold <[EMAIL PROTECTED]> wrote:
Hi, This is a best practices question. What is the impact of component level inheritance as far as performance is concerned? Is the the best solution to keep components as flat as possible? Thanks bjorn -- View this message in context: http://www.nabble.com/Tapestry-5-Component-Inheritance-and-Performance-tf3634042.html#a10148171 Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com
