you need a thread as Bruce suggested.
When the request comes in, start the thread.
Wait on the thread for 15-20 seconds (As you like).
If the thread does not complete in that time, then you respond to the client
("still working").
If the thread does complete, then respond with the complete status/result.

Check out the System.Threading namespace, the Monitor class, etc.

this article
[url] =en&lr=lang_en&ie=UTF-8[/url]
(all on one line)
(same thing)


"JTrigger" <jtriggernospam.nospam> wrote in message
> What I am trying to do is as follows:
> There is a web app that is used to request some information or have
> something created. When they submit the request it gets sent to a web
> service that then talks to any or all backend systems that need to be
> involked. If it takes longer than 15-20 seconds for the response, the
> client gets a message that they will be e-mailed the response. At this
> point, if the client closes the browser I want the web service to keep
> going. So, I cannot use the OneWay thing because many times the response
> happens rapidly, and I want to be able to give that response to the client
> in that case.
> "Brian Tyler" <brianmtyler> wrote in message
> news:u%23PC25qEEHA.3064tk2msftngp13.phx.gbl...
> > If you have control over the web service, then the easiest way is to
> > the web service method as "OneWay". This would cause the web server to
> > respond "instantly" and you can safely close the TCP connection.
> >
> > [SoapDoentMethod(OneWay=true)]
> > public void foo()
> > {
> > }
> >
> > "JTrigger" <jtriggernospam.nospam> wrote in message
> > news:uoWODvpEEHA.1456TK2MSFTNGP09.phx.gbl...
> > > I have a webservice that I want to call from a web app asynchronously,
> but
> > > not wait around for a result. Basically I want to fire it off and
> > > forget about it. I have figured out the asynchronous call all right,
> but
> > > when the client browser window is closed it sends an HTTP abort and
> kills
> > > the webservice. How do I keep the client from killing the web
> > >
> > >
> >
> >