SWF tidbit

[Cantor, Scott]

One partial reason why they execute the flow actions recursively is
probably because they allow you to execute multiple actions serially
inside one action-state using multiple <evaluate> elements, along with
various combinations involving that. I overlooked this because all of our
starting samples didn't illustrate this.

I think we're underusing this feature and making our life a lot harder
than it needs to be in these flows by defining a "proceed" event. The way
we should be doing this, and one that happens to actually work almost with
no changes from what we have, is returning *nothing* from the actions that
succeed.

By doing this, I think we can execute our actions serially within an
action-state, and have them transition any time there's an actual Event,
usually an error, or when something major needs to be done.

This almost just works because I decided not to require explicit proceed
signaling (I do it implicitly when nothing is signalled, inside my action
wrapper). If I take that bit of wrapper code out, we may be able to start
leveraging this with no code changes to the actions, and get rid of all
that recursion overhead.

I'm going to try that this week.

-- Scott