RE: [soapbuilders] How to handle multiple requests in "Applicatio n" scope
- Hi Naresh!
At least in the Apache SOAP/Axis world, scope refers to the backend object
which provides the service, not the entire SOAP engine. So it's certainly
possible to have many client requests threading through the network
connector, the servlet engine, and even the back-end object itself at the
You can think of this in precisely the same way as static objects - if the
methods in the object are thread-safe, you can have as many threads as you
want twining through your object's code at the same time. If certain areas
of the object are synchronized, then access to those areas will be
serialized appropriately. It's the same for network-accessible objects -
each network request might start a separate thread in the application
server, and those threads will happily access any thread-safe code in
parallel. It's only when they encounter synchronized code that the threads
From: Naresh Agarwal [mailto:nagarwal@...]
Sent: Thursday, September 27, 2001 9:59 AM
Subject: [soapbuilders] How to handle multiple requests in "Application"
I want to ask one thing about Soap implementations
If we deploy some service in "Application" scope (in Apache Soap or in
MS-Soap), this means the same instance of Soap Server would be used to
serve all the requests.
Now in this case, Soap server wudn't able to handle multiple client
requests, as there is only one instance of Soap Server, which is serving all
Is there any work around for this ??
Does Multi-threading is of any help in this case?
This group is a forum for builders of SOAP implementations to discuss
implementation and interoperability issues. Please stay on-topic.
To unsubscribe from this group, send an email to:
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/