Yeah, that was also my summation of this Interface.
As you say, I don't mind my servlet dealing with multiple threads as long as
two threads aren't heading for the same business object / controller!
So maybe we need the equivalent of "SingleThreadedBusinessObject" !?
What has been useful so far is to at least appreciate that I need to write
*some* logic to deal with this but it seems like a valid approach.
Russ
----- Original Message -----
From: "Dmitri Colebatch" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, June 20, 2001 12:46 AM
Subject: Re: multithreaded beans, struts, doing it right...
> (o: shit... I've just gone and re-invented the wheel..
>
> On Wed, 20 Jun 2001 09:29, you wrote:
> > 1) that there is some generic facility I can use to do this in tomcat
> yes there is, kinda, but I dont know it will do what you need. If your
> servlet implements SingleThreadedModel then tomcat will ensure that
multiple
> requests are not passed to the instance at once. But this doesn't mean
> tomcat cant handle multiple requests at once by creating multiple
instances.
> And because your business logic isn't in the servlet, but in another
object
> which is in the session, you'll still have the same problem.
>
> cheesr
> dim
>
