RE: How does apache soap deal with multiple requests?

[Oleg Timofeyev <li...@2xdigi.com>]

Hmm I can see how it can be a problem with application scope, but if you use
session, doesn't each session creates a separate instance and will not
affect other methods. For example if one client calls a method and some
member variables are set, and than another client accesses some method that
checks those member variables, will those calls overrun each other and
second client will get first clients variables. I dont think its the case,
but maybe I am wrong :) Please let me know what you think.

Sincerely,
Oleg

-----Original Message-----
From: Bono, Chris [mailto:chris.bono@zilliant.com]
Sent: Thursday, November 01, 2001 8:57 AM
To: 'soap-user@xml.apache.org'
Subject: RE: How does apache soap deal with multiple requests?


>>It seems reasonable to believe that a web service will have
>>more than one request at a time. My query is how does the
>>apache-soap server deal with multiple requests. If you use it
>>in combination with Tomcat does it simply follow Tomcat's
>>rules where nothing is thread safe and it is down to the
>>developer to handle concurrency issues and load balancing.

Yes. It follows the Serlvet spec in that regard. If you look at
org.apache.soap.server.http.RPCRouterServlet you can see that the
doPost method is not threadsafe. I just came across some issues
when attempting to cache a Provider amongst clients.

>>CORBA can use various concurrency models dependent on the
>>implementation including thread pools, thread per request
>>etc. How does apache soap deal with these issues? These
>>issues are important if you are going to design architectures
>>that use web services.
>>
>>Thanks in advance.
>>
>>Darren Marvin
>>Tel: +44 23 8076 0834
>>Fax: +44 23 8076 0833
>>mailto:djm@it-innovation.soton.ac.uk
>>http://www.it-innovation.soton.ac.uk
>>