My team has been tasked with designing a workflow driven web application. I need some advice about the design
Workflow should be dynamic. Meaning, users can define workflow through some interface and implement those workflows in a given scenario (the definitions will remain in SQL 2008 database) scenarios are defined by business and will never change. Therefore there are only 2 types in scenarios, a workflow can be defined. Workflow is not linear any kind of state will run workflow. The state will also be dynamic, but will only exist in one workflow.
I see examples of workflow and state machines and my head is spinning. I'm not sure whether I develop the O Lewer Workflow Foundation or some of the things that we develop. I have seen and think that this can work, but I am not sure that the complete implementation of the state will work for us.
You can use it WF4 I have never used the objectflow, Can not comment in, but it is in a memory solution and with the ASP.NET Web site hosted in IIS, this means that you will occasionally recycle IIS and lose the state as AppDomain. Generally there is not a big problem as it is not frequent but WF4 InstanceStore will take care of it, it also allows you to run on a web form without sticky sessions and migrate to workflow machine from the machine.
Another good thing is that the workflow designer can rehost its one WPF control in your own application. ASP.NET or Silverlight is not in the app but you can provide a smart client so that users can use VC in 2010 using Workflow Defration using Workflow Defriction.
The biggest problem with WF4 is the asynchronous execution nature. You must use a synchronization context syntax to execute the activity, and wait for the workflow to be lost in the new state before returning the resulting HTML to the browser.
Comments
Post a Comment