Keeping server-side object alive

I'm trying to wrap a protocol behind a web service, the problem is that
part of this protocol involves a thread that waits for asynchronous
events and replies to commands - one of those events is to indicate if
you have successfully logged on.

This thread needs to run for the lifetime of the session. I can keep
the object alive, but as soon as the startup/login web method ends the
event thread dies with it so I don't get any more messages.

Is there a way to keep an object alive with threads running in a web
service or will I have to start looking into remoting (or any other
solution appreciated!).

--Liam.

.

Relevant Pages

  • Re: Why is soap.inproc not supported for production use?
    ... > I am designing a web service using WSE 2.0 that has flexible deployment ... I'm obviously going to use the HTTP transport. ... That is, the soap.inproc protocol, which can be used to send ...
    (microsoft.public.dotnet.framework.webservices.enhancements)
  • Web Service
    ... Protocol with name 'HttpPost' is not recognized. ... I know that I can just name the input fields on a normal HTML form to ... match my web service method parameters and change the form action to point ...
    (microsoft.public.dotnet.framework.aspnet.webservices)
  • Re: Send XML without SOAPEnvelope wrapper?
    ... I've written a .NET 2.0 web service that takes an XML file as input. ... The envelope is part of the protocol, ... the header, then you need to put them there by defining them in your web ...
    (microsoft.public.dotnet.framework.webservices)
  • Re: Adding Research Services
    ... "speak" a particular protocol. ... front page of Brittanica's web site, not a web service (if indeed they ... >> Mary Sauer MSFT MVP ...
    (microsoft.public.word.newusers)
  • Wrapping a web service
    ... I want to wrap a web service in an assembly, ... GetStatus is the name of the method. ... The exception gets thrown on the call to this.Invoke inside the ...
    (microsoft.public.dotnet.framework.webservices)