title: Windows Workflow Foundation WF4 - Workflow hosting
body: <p>For a client the system we're creating must support the following:<br>
  - It must be possible to run multiple workflows, and multiple instances of the same workflows with a different context (different data/business objects).<br>
  - Some workflows will be long-running, involve multiple users/client session and waiting for external user input. So the workflows must be able to be persisted and respond to some signal from a client app. And it also  means that the execution of workflows must be done on a server app (right?).<br>
  - I want to be able to run all kinds of workflows on the server app, and I do not want to have to re-deploy the server app when a workflow changes.  </p>
  
  <p>My first thought was Workflow Services. After a lot of research I concluded that this is not the right path since Workflow Services basically gives the possibility to execute activities at a remote location from a workflow started in a client app. Is this correct? Or can I use Workflow Services for the scenario above? Most examples and/or tutorials are basically a ReceiveSignal/Send combination with some logic in between.  </p>
  
  <p>Basically I want to initiate (from a client app) the start of a workflow with a specific context (in the workflow server app).  </p>
  
  <p>What is the best approach?</p>
  
  <p>Any help is very much appreciated!</p>