I am new to WF ..and I have a basic question.

WF has two kinds of queues:
1. WF program instance's Scheduler queue , which is managed by WF runtime
2. WF program queue , a data structure, where external entities (Hosts) deliver data to dormant workflows.

Physically which data structure is employed for these logical queues What would be the table name (If it is a table in SQL server 2005).

Re: Windows Workflow Foundation WorkFlow Queues

ElifOn - MSFT

If it is not public then we would't be able to disclose more information on which data structure/technologies are used for which stuff. However if you have any product specific problem related questions we would be happy to help you and eager to hear feedback.



Re: Windows Workflow Foundation WorkFlow Queues


Fine, if it is propriterary then leave it that . But conceptually probably you can help. Here is where I am coming from.

My scenario: The stimulus for a workflow to resume comes from an external "Service" based on some business criteria.

Now the initial idea (before I knew of WF) was to have this external "service" log the request to a Queue (MSMQ kind of queue).

Now WF provides the same fiunctionality via WF program Queue , which serves my purpose.

But what are my deployment considerations now I mean, If I went this route...What would be my deployment components.

Framework 3.0 and SQL Server 2005

As you can see I am confused.

Re: Windows Workflow Foundation WorkFlow Queues


Never Mind ...found my answers "passivation"

Re: Windows Workflow Foundation WorkFlow Queues

Kavita Kamani - MSFT

Can you clarify the issue and the answer you found for future readers of this post

Re: Windows Workflow Foundation WorkFlow Queues


The "Program Queue", which an activity creates and where it recevies external stimulus is a logical queue and each workflow instance have their own queue .

This would one of the entities, among others, that would be persisted in a durable DB when WofkFlowInstance.UnLoad() is called typically when the workflow idles.

Now details of how runtimes persists and rehydrates this logical "Program Queue" is apparently proprietary, I am told.

But from the deployment stanpoint , Framework 3.0 and sql server 2005 will suffice. I do not need any special queue like MSMQ etc.