How many workflow work cycles should an Asp.Net application execute?

Question

There do not seem to be many Windows Workflow Foundation gurus :(

Here are some issues that I am facing:

How many workflow work cycles should an ASP.NET MVC application execute? One per application, per session, or per request?

How often should you start and stop a workflow environment? Once per application instance once per session or once per request?

What are the pros and cons of this or that action in the above options?

Any comments or suggestions are welcome,

Thanks,

Cullen

Answer 1

. , , , . , .

- SqlWorkflowPersistenceService. IIS , . , , .

ManualWorkflowSchedulerService, ASP.NET, . useActiveTimers="true", .

, , . IIS , .

, , , . , , , , , . , .

Answer 2

ASP.NET MVC?
, ( )

?
, ,

con , , .

, , , .