In my last post I said "it was not threadsafe". That is incorrect. In its current state it *is* threadsafe since it only deals w/ local variables. If you decide to extend the base functionality to add caching of providers etc.. then you need to deal with the threading issues.
My bad, Chris >>-----Original Message----- >>From: Bono, Chris [mailto:[EMAIL PROTECTED]] >>Sent: Thursday, November 01, 2001 10:57 AM >>To: '[EMAIL PROTECTED]' >>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:[EMAIL PROTECTED] >>>>http://www.it-innovation.soton.ac.uk >>>> >>
