the scalability is really defined by the app server; it is the one that creates the threads and the servlet instance to handle it. But your endpoint can be in an object created per message (The default), per session, or a singleton; the latter may scale better if you code for re-entrancy
----- Original Message ----- From: "Roy Wood" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, February 05, 2003 06:33 Subject: Scalability, Multiple Threads/Objects? I've read through the Axis docs and can't seem to answer this question, and am hoping that someone else out there can help. I'm looking at deploying a SOAP/Axis service, and am concerned about scalability. It seems the logical thing to do is have several instances of my code running to service multiple incoming requests from the clients, but I can find no definitive statement that this is what Axis does. Anyone have anything to comment there? I'm deploying within Tomcat, so perhaps it is handled at the Tomcat level? -Roy "Disclaimer The opinions expressed in this message are strictly personal and do not necessarily reflect those of FiLogix."
