CODEWITHSUNDEEP
c#iisasmx
Night Walker
Night Walker

Reputation: 21280

long running tasks under asmx service hosted on IIS

I have some legacy ASMX IIS hosted service. Client applications make subscribe or unsubscribe to the web service. Via some internal to the web service logic it needs to send messages to the subscribed applications periodically.

What is the best way to do the part of the long running task ? I understand opening Thread with long running task not a good idea to do under IIS.

Upvotes: 0

Views: 440

Answers (2)

John Saunders
John Saunders

Reputation: 161821

ASMX services cannot do what you're asking for: they cannot just decide to send a message to the client. All they can do is respond if the client requests it.

You can hack around and come up with one method to start the long-running task, and another method to poll for the status of the task. This works, but it can be expensive.

The better model is to perform the long-running task in a separate Windows Service. Have that service host a simple WCF service which will only be used by the main service (the one that talks to the clients). The main (WCF) service would use a Duplex channel to communicate with the clients. That way, it can "call" the clients whenever there is news about one of the long-running tasks.

Upvotes: 3

Eugen
Eugen

Reputation: 2990

Usually in such cases when you don't have a way to push the result back, create an unique ID for the long running task and sent it back to the client, after that run the task and have a table in database or something else where you store the status of the task. The client will pull periodically the service to see the task' status by given ID. Once it finds the task is completed it will retrieve the result. And is completely fine to have a thread running inside IIS doing its job.

Upvotes: 1

Related Questions