commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tim OBrien <>
Subject Re: [SCXML] Decoupling Execution Context from the SCXML Model (WAS: [scxml] a few observations, issues before release)
Date Wed, 18 Jan 2006 16:25:46 GMT

--- Rahul Akolkar <> wrote:

> On 1/14/06, Tim OBrien <> wrote:
> <snip/>
> > 2. Decouple Execution Context from the SCXML Model
> >
> Most of your observations are correct. We need effective cloneability
> and/or decoupling, re-parsing is a waste. If you have any ideas, do
> let me know. I'll spend some time on this during the rest of the week,
> primarily just starting a new thread here, will clip the email length
> in the next posts.

Created a place holder issue for the task of identifying the appropriate way to do this:

Do you want to take a stab at this?  I had some ideas about the semantic impl, should we both
out some ideas independently in two different branches and then see what bubbles out of
independent effort?

> This actually was one of the things I had in mind between sandbox
> graduation and release.

And, this is I guess one of the central issues with releasing scxml into commons (again, not
I disagree with it being in the commons).  Althogh I think there is some room for flexibility
after a release, commons components are limited by the fact that we haveto try to maintain
compatibility between major releases.  

Becuase of this, I think that the public interface of scxml needs extra scrutiny before a
(and to me the 1.0 release happens at the same tie as promotion).

> -Rahul
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message