tags:

views:

38

answers:

1

I have a WCF service (hosted in IIS 6) with two services, FileMonitorService ans JobService. In one of FileMonitorService's methods I want to call a method in JobService through WCF. This method in JobService is executed asynchronously (fire and forget).

I suppose it'd be easy enough use a Thread Pool and signal when they are all done.. I'd rather use WCF though (this is a personal project, so I'm just trying out new things).

edit: I came across these two posts, but they addressed WCF services across different servers.
Calling a WCF service from another WCF service
calling a WCF service object method in another WCF service

edit 2: Clarification on question:

Less a question I suppose than more of a request for thoughts on the approach.

+1  A: 

Doing it through WCF only adds overhead so you should call the method in JobServices directly unless you have a compelling reason to not to do so. Given the limited amount of context, I would stick with the ThreadPool if I were you.

Alfred Myers
I agree I think. As I mentioned in my comment above, I realized that instead of a service, what the initial WCF service is basically doing is kicking off a workflow.. So I think WF may be the best solution in this case.
Bryce Fischer
Nope, went with your suggestion Alfred and the JobServices uses ThreadPool directly.
Bryce Fischer