Understand the state transtion

Question

0.00/5 (No votes)

See more:

I am using the stateless framework.

But I do not fully understand the state concept.
For example:

C#

phoneCall.Configure(State.Ringing)
    .Permit(Trigger.HungUp, State.OffHook)
    .Permit(Trigger.CallConnected, State.Connected);

Does it mean the workflow is from Ringing=>OffHook=>Connected unconditionally?

What I have tried:

I read the article. It says A transition’s Trigger is scheduled when the transition’s source state’s Entry action is complete.

But in my code example, there is no OnEntry in the configuration.

Posted 11-Mar-16 13:42pm

zhshqzyc

Updated 11-Mar-16 19:01pm

Add a Solution

2 solutions

Solution 2

Quote:
Does it mean the workflow is from Ringing=>OffHook=>Connected unconditionally?

No, not as I read it - it reads to me as if the state is ringing, you can go to OffHook OR Connected depending on the trigger/event

Posted 11-Mar-16 13:57pm

Garth J Lancaster

Comments

[no name] 13-Mar-16 14:50pm

Does the order matter?
Say
A:

phoneCall.Configure(State.Ringing)
    .Permit(Trigger.HungUp, State.OffHook)
    .Permit(Trigger.CallConnected, State.Connected);

And
B:

phoneCall.Configure(State.Ringing)
        .Permit(Trigger.CallConnected, State.Connected)
		.Permit(Trigger.HungUp, State.OffHook);

Are A and B same?

Garth J Lancaster 14-Mar-16 7:04am

I cant say for sure - without going through the Stateless library - its does say it allows "Hierarchical states" - but to me, what youve shown is the same state, with two legal transitions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

BillWoodruff · Accepted Answer · 2016-03-11T19:01:00

The "Stateless" project is an interesting one, but, I think the choice of the name is confusing: of course it maintains internal state; and, the "state machine" concept is all about "state" !

The code you cite sets up a "rule" for a given "state:" "ringing."

It defines two possible "transitions" from "ringing."

The "Entry" action will refer to a dynamically created event handler that the class creates at run-time.

Keep in mind that the "Stateless" project does not use Microsoft's Windows WorkFlow Foundation; it also uses very complex, and advanced, progamming techniques.

You might get some benefit by studying WWF in terms of insight into general "state machine" principles: [^].