WSE 3.0 TCP Multi-Threading Advice

[=?Utf-8?B?VGlt?=]

I have written both a client (SoapClient) and server (SoapServer) application
using WSE 3.0 with the TCP transport. These are completely standalone
applications (the Server runs as a Windows Service).

The one thing I am struggling with is how to adequately add multi-threading
to the server and was wondering if anyone can offer help and advice?

Within the WSE documentation there are two items which I have not found a
great deal of information on, but appear, to be relating to a potential
underlying threading model and I was wondering if this is indeed the case?

The first is the connectionLimit configuration setting and the other item is
the DispatchModel on the SOAPReceiver object which can be set to the
Concurrent dispatch model.

Have I missed this in the documentation or could someone provide me with
some pointers?

I am presuming there is a threading model dealing with the TCP connections
to my web service (goverened by the connectionLimit) which can operate
concurrently if I configure the dispatch model to concurrent - is this a
correct assumption?

Obviously I could put multiple-thread support in my service class (derived
from SoapService) and essentially use my registered SoapMethods (using the
SoapMethodAttribute) as a broker into a connection manager (and service
thread pool) but it seems like the wrong layer (way to high up the
architecture) to implement this. Can anyone please offer any architectural
advice in this area?

Many Thanks,
Tim.