D
dave
One thing i'm finding very quickly as my servlets become more logically
condensed, is that an "object" in the sense of "object oriented design"
becomes restricted to a "webpage/servlet". How do you enterprise programmers
manage to effectively incorporate OO design (in the architecturally broad
sense) within an application that, perhaps more efficiently benefits in
performance from one servlet rather than 12 servlets performing the logical
functions of what 1 servlet spaghetti coded can do?
condensed, is that an "object" in the sense of "object oriented design"
becomes restricted to a "webpage/servlet". How do you enterprise programmers
manage to effectively incorporate OO design (in the architecturally broad
sense) within an application that, perhaps more efficiently benefits in
performance from one servlet rather than 12 servlets performing the logical
functions of what 1 servlet spaghetti coded can do?