I've actually been working on a program for quite some time now, and I have this intuition that when it comes time to finally performance
test or something, I'm going to get burned.
Basically, my entire
servlet application only extends Servlet once. That servlet instantiates my own version of a session object, which I of course insert into the HttpSession object. That (my) session object manages my primary 'current' manager and all of (what I call) my 'sub' managers which direct a user across whichever task path they take. Specific pages extend Containers that extend a base page, and essentially these classes all digest whatever params I've conjured up from the base servlet into some set of html that returns, of course, via the primary servlet.
This seemed like a great idea a long time ago, just being able to avoid whatever threading issues and instance variables that came up -- just having one servlet and a few hundred classes that churned out various pages in html(Strings).
With this superficial discussion of my app, does anyone see anything inherently wrong with this design? Is this an inane design? Is this a common sense design? Not enough info? Is there a specific reason(or benefit) to extending servlet in each possible page?
Thanks in advance...
[ February 11, 2002: Message edited by: matt horton ]