title: WCF right for all cases?
body: <p>I'm building an application that will distribute its processing over a farm. In my basic design I have two services: </p>
  
  <p>A "controller" which watches for new work, queues it up, and manages the results.</p>
  
  <p>A "worker" which binds to a particular controller. The worker will check out work from its controller, and push the results back.</p>
  
  <p>In the breif look I've had at WCF, it seems to imply a MEST style message-passing SOA. This mechanism doesn't seem to jive with the types of communication &amp; coordination I'll be doing.</p>
  
  <p>Am I mixed up on what WCF is? Is there still a place in this world for .NET remoting? Or am I thinking about the problem in a jurassic, pre-WCF mindset.</p>
  
  <p>Edit:<br>
  Left out some detail. The rub is that I need to timebox the work. If a workitem is checked out for too long, I should be able to error the whole thing. The examples I've seen all seem to take a "send and forget" stance towards the outgoing messages. I need a deterministic result or error in a reasonable timeframe. Hope that clarifies.</p>