fsm:use_fsm
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
fsm:use_fsm [2007/04/29 14:02] – fgm | fsm:use_fsm [2010/11/11 09:39] – fgm | ||
---|---|---|---|
Line 14: | Line 14: | ||
===== Controlling the FSM operation ===== | ===== Controlling the FSM operation ===== | ||
+ | ==== Directed work with the " | ||
+ | A special built-in event is fsm:: | ||
- | ==== Directed work with " | + | This event can be turned off by setting the FSM "$idle" |
- | A special built-in event is "idle" | + | Syntactic sugar: the idle() |
- | This behaviour can be turned off by setting the FSM " | + | ==== Filtering events ==== |
- | ===== Filtering events ===== | + | The OSInet FSM has three event processing modes, controlled by the {get|set}_event_mode methods: |
- | + | ||
- | The OSInet FSM has three event processing modes, controlled by the " | + | |
* fsm:: | * fsm:: | ||
Line 32: | Line 32: | ||
* Switching from fsm:: | * Switching from fsm:: | ||
- | ===== Disabling | + | ==== Disabling |
+ | Firing of post-event actions is enabled by default, but can be disabled by setting the $allow_actions property to false. | ||
+ | |||
+ | In that case, applications can still decide to fire the event themselves by reading the fsm_action field in the fsm_result returns by fsm:: | ||
===== Example ===== | ===== Example ===== | ||
Line 39: | Line 42: | ||
For a very basic FSM going just from initial to final randomly, building the table and transitions can look like: | For a very basic FSM going just from initial to final randomly, building the table and transitions can look like: | ||
- | <php> | + | <code php> |
class foo extends fsm | class foo extends fsm | ||
{ | { | ||
Line 66: | Line 69: | ||
} | } | ||
} | } | ||
- | </php> | + | </code> |
+ | |||
Application code not involved in the FSM operation can use the FSM apply_event method($event_name) to submit an event to the FSM. Only allowed events for the given state the FSM is in are allowed: submitting other events throws an exception. | Application code not involved in the FSM operation can use the FSM apply_event method($event_name) to submit an event to the FSM. Only allowed events for the given state the FSM is in are allowed: submitting other events throws an exception. |
fsm/use_fsm.txt · Last modified: 2020/11/23 17:23 by 127.0.0.1