WS kø?

det er IIS der behandler dine request's og det er så og sige kun din netforbindelse og computer der sætter grænsen for hvor mange requests den kan behandle af gangen. Så nej, umiddelbart sætter den dem ikke i gø, men behandler den samtidig, dvs at IIS opretter 10 instanser af din webservice-klasse.

Okay! Har du en url, hvor jeg kan læse mere om det!?

om hvilket? hvor mange connections IIS kan klare eller?

At den instansierer en klasse/kald. Ville det være en fordel at lave WSen asynkront?

Jeg har fundet det her:

We will begin our walkthrough at the point where the consumer sends a properly
formatted SOAP message to the target server requesting the CTemp method of the
CTemp Web service.

1. The IIS Web server hosting the CTemp Web service receives the request
message (technically, an HTTP -SOAP request).
2. The URL is interpreted by the Web server to determine what ISAPI filter
is responsible for handling the request (based on the file type). Because
the URL points to the Web service entry point file (the ASMX file), the
request is passed along to the ASP.NET ISAPI filter.
3. The ASP.NET ISAPI filter passes the request to an instance of the .NET
HTTPRuntime class, which is hosted within an IIS application process.
The movement of the request from the ISAPI filter to the HTTPRuntime
class completes a transition from unmanaged to managed code.
4. The ASP.NET HTTPRuntime class is responsible for handling all
incoming HTTP requests. The runtime resolves the URL to a specific
application and then dispatches the request to that application. Web
services are handled by the .NET WebServiceHandlerFactory class.
5. The WebServiceHandlerFactory deserializes the SOAP payload from the
request, creates an instance of the CTemp Web service implementation
class, and executes the CTemp method, passing the input arguments.
6. The ASP.NET runtime takes the result of the CTemp method call and
serializes it into a SOAP response message. This message is then
added to the payload of an HTTP response and delivered back to the
client (in this case, our proxy class).

As you can see, a lot goes on behind the scenes of a Web service method request.

Although this overview gives you an idea of what happens to a Web service request while it is being processed, it is by no means a complete picture.

Many details within each of these steps have been left out for brevity (and understandability). However, this short tour should make it easier to see how the various pieces of the puzzle fit together.

det er nemlig rigtigt... :)