Posted By:
Manish_Patel
Posted On:
Thursday, September 5, 2002 03:15 PM
Folks, We recently had a consultant look over our design and he recommended using a Dispatcher-View pattern over our Service-to-Worker pattern because of performance. He contends that in a Service-to-Worker pattern, where the Controller is more responsible for processing the form data from JSP's, has a performance overhead since all requests come to the controller. The benefits to a Dispatcher-View pattern, in which the final JSP is responsible for populating its own view, is that when the Controller forwards the request, the server executes the resulting JSP in a separate virtual port. This, he says, is advantageous since the processing from that point on is done by a single thread. Anyone care to comment?
More>>
Folks,
We recently had a consultant look over our design and he recommended using a Dispatcher-View pattern over our Service-to-Worker pattern because of performance. He contends that in a Service-to-Worker pattern, where the Controller is more responsible for processing the form data from JSP's, has a performance overhead since all requests come to the controller. The benefits to a Dispatcher-View pattern, in which the final JSP is responsible for populating its own view, is that when the Controller forwards the request, the server executes the resulting JSP in a separate virtual port. This, he says, is advantageous since the processing from that point on is done by a single thread. Anyone care to comment?
<<Less