Cor Ligthert wrote:
I don't see as often not any need for a thread in this because all that
you do in the main thread is the proces.
Sorry, Cor, actually this is for a completely different application...I
should have explained.
The situation is:
1) A web service that runs a Sql Server sproc and outputs a text file.
2) The sproc can take up to 10 minutes to run.
3) The consumer of the web service does not need to know if the file is
produced -- it just needs to kick off the process.
So, I thought the web service could:
1) Receive the request.
a. Spawn a thread to run the sproc and output the file
2) Immediately return a response to the consumer that says "message
received". And then the consumer would be released ( not subject to http
timeouts and so on. )
--
Texeme
http://texeme.com