Any RequestDispatcher.forward() call has roughly the same performance impact as what the container has to do on any original HTTP request (map the request to a particular servlet, start that servlet as needed, and call the service() method). Since it all happens on the server side, it's generally a very small amount of time. In most cases, it will be an order of magnitude faster than anything that requires an HTTP redirect.1. Are there any performance issues involved when an Action class forwards to another?
The only possible way this could matter is if you run out of memory, which is typically not the issue. The most common performance bottlenecks I've seen are (in priority order):
2. Does the number of Actions created in a web
application affect the overall performance of the
application?
* Database access
* Network performance
* Locking too aggressively
Performance tools can help you analyze where the issues are for your particular application.
Craig
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
