DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUGĀ·
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=38274>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED ANDĀ·
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=38274

           Summary: [scxml] Add another use case that isn't Voice (RDC) or
                    MVC (Shale)
           Product: Commons
           Version: unspecified
          Platform: Other
               URL: http://jakarta.apache.org/commons/sandbox/scxml/usecases
                    .html
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Sandbox
        AssignedTo: [email protected]
        ReportedBy: [EMAIL PROTECTED]


SCXML has two good use case documents, one is about RDC and one about Shale
dialogs.  There are a good start, but it would be helpful if SCXML had another
usecase that wasn't tied to either a voice application or a web MVC framework. 
Something at a conceptual level that people looking to use SCXML for a general
finite state machine can relate to without having to be familiar with another
framework.

The question is, what should this example be?  We could use the Microwave
example from the working draft, but that might be too much for a quick
introduction.  Instead it might be better to choose something that doesn't have
parallel states, maybe the status of a document in a content management system
with four/five simple states and simple transitions that just shows off the
basic usecases of the state machine execution environment in a standalone
environment.

-- 
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to