I am currently working on developing a web service that must use multithreading to achieve the required functionality. Because web services are stateless I'm having a lot of difficulty keeping the auxillary thread alive on the server. When the client connects to the server a new object, serverObject, is created and saved as a session variable. During the creation of the serverObject it generates a second thread to run in the background. As soon as the initial connection between the client and server is completed the auxilary thread dies.
I had hoped that by saving the parent object as a session variable all child objects, including threads, would stay alive. I'm finding that all of the other child variables and objects, including event callbacks, are maintained so this is specific to threading. Does anyone have any suggestions on how I can keep this thread alive? Thanks, Ned. KUKA Roboter GmbH. =================================== This list is hosted by DevelopMentor� http://www.develop.com NEW! ASP.NET courses you may be interested in: 2 Days of ASP.NET, 29 Sept 2003, in Redmond http://www.develop.com/courses/2daspdotnet Guerrilla ASP.NET, 13 Oct 2003, in Boston http://www.develop.com/courses/gaspdotnet View archives and manage your subscription(s) at http://discuss.develop.com
