This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
In my app I've got a lot of servlets where I have to repeat a lot of code all the time. So I decided I would write a parent class than all my servlets would extend it.
Here is the 3 main methods from my parent class:
I override the doIt method in my children classes. My question is:
Does this approach have any performance problem? Is it slower than repeat all the code in the servlet classes?
I know the container allocates a thread (or grabs one from the pool) for a new request. So all the requests have a unique stack and a unique thread. But isn't it a problem that they all call the same methods first? (doPost and handleExceptions from the parent)
I'm always confused about this kind of situation. I don't really know how it happens. There is one method from one class which is not synchronized. A tons of requests get it (it = the same unsynchronized instance method from the same instance of a class, or the same unsynchronized static method from the same class). How does it happen in detail? How can that much request execute the same (the only one) method concurrently?
Inheritance is not slower than repeated code. Repeated code is an anti-pattern and something you should seek to avoid. If a method is not synchronized, it doesn't matter how many callers call it at the same time.