RE: Implement TCP with scxml compliant state machine

FWIW we implement some of our SIP stack using SCXML state machines to capture the SIP flow (the SCXML implementation is a C++ one where the external events are actually C++ "event" objects that get delivered to other threads).  Because some of the SIP signaling specifications are complex with lots of contingencies the SCXML is easier to develop and test than the "native" code driven state machines we'd used before.  So I think there is benefit there for handling lots of different protocols (assuming your SCXML interpreter is robust).

From: chris nuernberger [mailto:cnuernber@gmail.com]
Sent: Monday, February 11, 2013 10:49 AM
To: VBWG Public (www-voice@w3.org)
Subject: Implement TCP with scxml compliant state machine

It would be extremely interesting to implement the TCP stack with an SCXML state machine.

You could then compare its characteristics (performance, security, correctness, flexibility) with a native C implementation and see where the benefits lie.

I wonder if any OS grad students would be interested in that for a summer of code project.

Chris

--
A foolish consistency is the hobgoblin of little minds - Emerson