I'm looking at a few different approaches to a problem: Client requests work, some stuff gets done, and a result (ok/error) is returned.

A .NET web service definitely seems like the way to go, my only issue is that the "stuff" will involve building up and tearing down a session for each request. Does abstracting the "stuff" out to an app (which would keep a single session active, and process the request from the web service) seem like the right way to go? (and if so, what communication method)

The work time is negligible, my concern is the hammering the transaction servers in question will probably get if I create/drop a session for each job.

Is some form of IPC or socket based communication a feasible solution here?

Thoughts/comments/experiences much appreciated.

Edit: After a bit more research, it seems like hosting a WCF service in a Windows Service is probably a better way to go...