There is gonna be always a stub per client (on the client side of the conversation) but the implementation of the skeleton can vary. You may have a skeleton per each stub or vendor can implement one "master" skeleton that will handle all requests. In this case the stub will also send some sort of session information so skeleton can distinquish between different clients.
SCBCD 1.3<br />SCJP 1.2<br /> <br />"Every time I learn something new, it pushes some old stuff out of my brain" H.Simpson
Yeast devil! Back to the oven that baked you! And take this tiny ad too: