|
that is the
problem with MVC model. There is a huge bottle neck at the servlet that brings
down the efficiency. In a MVC we have only one servlet if we have more than that
.
in that
scenartion two clients can modify the same data.
Cheers!!
raj
What makes you believe that the Controller Servlet in the MVC
model has to be a Singleton Class.
Another thing as per my limited knowledge having a singleton class
doesn't mean that it implements a SingleThreadModel interface.It only means
that whenever the static getInstance method of the class is called
only one instance would be returned and the Class has a private
constructor which helps in achieving the above mentioned behaviour.
The performance of an application could suffer if the Controller
Servlet implemented the SingleThreadModel interface in my opinion.
Looking forward to your (Mr. Sandhu) as well as
others comments.
----- Original Message -----
Sent: Thursday, August 02, 2001 12:35
PM
Subject: Re: MVC Issue
There is no
need for synchronizing the process method in the request handlers in the MVC
model.
As the
controller servlet is a singleton class (implements single thread model)
i.e. two threads cant call the service method concorrently. so no two
clients can call the same process method of the request handler. you can say
Servlet works as a synchronizing agent. (Or actually synchronization never
takes place/ reqiured ).
Cheers!!
raj
Hello Jspians,
I'd just like to get your
comments on the following :
In the MVC model, each action class has a process(...) or similar
method.
I'd like to know if there is a need to synchronize this method.
Looking forward to your comments.
|
