StateCoder Features

StateCoder

State machines can be defined statically using attributes or dynamically.
Flexible thread control - from using a single thread to support unlimited state machines to assigning each state machine its own thread.
Largely self-synchronizing - helps eliminate the chance of data corruption, race conditions and deadlocks.
Supports custom message sources.
State Machines can be nested - one machine can start another, then continue when the "child" state machine ends.
Includes standard message sources including timers, streams, exceptions and generic support for any .NET asynchronous operation (IAsyncResult).
Messages can be any .NET object.
States can support any number of message sources, and can redefine message sources as the state machine runs.

Management of asynchronous operations: Especially useful for managing large numbers or varying numbers of asynchronous operations
Dramatically reduce the number of threads needed to perform background operations (especially useful for objects that support multiple clients)
Selective use of between-request processing for ASP.NET and web services can dramatically improve user response, while using minimal server resources
Encapsulating sequences of asynchronous operations (wrapping them into a single event or wait operation)
Protocol Implementation. Internet or other protocols are almost always based on state machines
Data format conversions. State machines can be used to parse incoming data and perform operations based on the results, including generating output data in a different format
Do-it-yourself transactioning. State machines can define transaction based objects that don't use COM+/MTS