We should have both.
I like subclassing when I change the basic implementation (data level), and hooks/callbacks/plugins where I need to
add code that responds to events of the basic web application flow.
Agreed.
In my option, the desire of users to subclass basic classes like Session or Request is most probably a sign of some design deficiency. It should be possible to _collaborate_ with the framework to achieve developer's goals instead of thrashing it. ;-)
Of course, there could be situations where the user wants something very different that was not anticipated by the framework. In such cases he could use subclassing as a last resort.
------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
