Best archtiecture for long runnig workflow?

Hello,

I'm still not came over a good example for long running workflows with human interaction and don't see clearly the best architecture for it. Would a Windows Service be the perfect host? It should contain some Webservice interfaces. Especially the one to start it with.

Greetings, Andreas

[316 byte] By [Sha1-Hulud] at [2007-12-18]

«« Problem in Installing 64-bit Reporting Services
»» OLE DB COMMAND Programming Help

# 1

Can you give me a bit more information on what you are trying to do?

StateMachines can be run with Long running workflows, even to web services.

BillZunis at 2007-9-8 >

top of Msdn Tech,Software Development for Windows Vista,Windows Workflow Foundation...

# 2

Sorry for the late answer,. I'm not very familiar with this forums and lost this thread until I found the link "My Threads". I switched and use Message Queuing with a service to do my interaction and host the runtime in a winforms app (may become a service later). The problem with hosting the app directly in a webservice would be the timeout of the asp.net runtime?

Sha1-Hulud at 2007-9-8 >

# 3

The timeouts in web applications are in the browser for a request being responded to and also in the session state (default 20 minutes). These don't apply for long running workflow instances which can execute for an unlimited amount of time. When idle these workflow instances are persisted to permanent storage waiting for an event to start them back up.

There is an example of using workflow in ASP.NET at the workflow community site.

Regards,
Paul

PaulAndrew at 2007-9-8 >

Software Development for Windows Vista

Windows Workflow Foundation

Software Development for Windows Vista Hot Topic

Software Development for Windows Vista New Topic

Software Development for Windows Vista

Java / MSDN / Linux Tech / PHP Tech / MSDN DotNet / MSDN TECH / Health Library / Programmers Tech / visual basic Tech / Developer Tech / Ipod faqs / Msdn China Tech