Return-Path: 
 <commons-dev-return-83240-apmail-jakarta-commons-dev-archive=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-commons-dev-archive@www.apache.org
Received: (qmail 22770 invoked from network); 19 Jan 2006 20:17:46 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 19 Jan 2006 20:17:46 -0000
Received: (qmail 95308 invoked by uid 500); 19 Jan 2006 20:17:35 -0000
Delivered-To: apmail-jakarta-commons-dev-archive@jakarta.apache.org
Received: (qmail 95227 invoked by uid 500); 19 Jan 2006 20:17:35 -0000
Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:commons-dev-unsubscribe@jakarta.apache.org>
List-Help: <mailto:commons-dev-help@jakarta.apache.org>
List-Post: <mailto:commons-dev@jakarta.apache.org>
List-Id: "Jakarta Commons Developers List" <commons-dev.jakarta.apache.org>
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Delivered-To: mailing list commons-dev@jakarta.apache.org
Received: (qmail 95192 invoked by uid 99); 19 Jan 2006 20:17:35 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2006 12:17:35 -0800
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of rahul.akolkar@gmail.com
 designates 64.233.162.201 as permitted sender)
Received: from [64.233.162.201] (HELO zproxy.gmail.com) (64.233.162.201)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Jan 2006 12:17:33 -0800
Received: by zproxy.gmail.com with SMTP id 8so293875nzo
        for <commons-dev@jakarta.apache.org>;
 Thu, 19 Jan 2006 12:17:13 -0800 (PST)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=HTliI8b9ijBms8aMCNF4Ix1oLnoSvbZvJC1UkE6tmFAR8XWi53YUU9Z80hZN9V2RtH2Tg2+d/SxRtmhvgUG2wTw25a7vluUVhAZbyziwlFjPFf74WB8Bnrz105+TTI3aYL8WkQWw1sd3pStsheB8n07YKlBln6drxr8C/xAWNNk=
Received: by 10.36.251.34 with SMTP id y34mr822904nzh;
        Thu, 19 Jan 2006 12:17:13 -0800 (PST)
Received: by 10.36.24.16 with HTTP; Thu, 19 Jan 2006 12:17:13 -0800 (PST)
Message-ID: <ce1f2ea80601191217v31c373bfl6a2d559d22fac9ef@mail.gmail.com>
Date: Thu, 19 Jan 2006 15:17:13 -0500
From: Rahul Akolkar <rahul.akolkar@gmail.com>
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: [SCXML] Decoupling Execution Context from the SCXML Model (WAS:
 [scxml] a few observations, issues before release)
In-Reply-To: <20060119154135.87823.qmail@web413.biz.mail.mud.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <ce1f2ea80601181554i6f0dc789se787dcef0482c58f@mail.gmail.com>
	 <20060119154135.87823.qmail@web413.biz.mail.mud.yahoo.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

On 1/19/06, Tim OBrien <tobrien@discursive.com> wrote:
>
<snip/>
>
> Even if a state is associated with a context it doesn't necessary mean th=
at there needs to be a
> relationship with an actual context item.
>
> I guess this is a case of "well....wouldn't it be helpful to be able to p=
articipate in that
> Working Group".  :-)
>
> The thing that I think is important for the SCXML working group to know i=
s that for some
> applications to be feasible a state machine must be efficient, not tied t=
o execution context and
> able to be shared at runtime by "possibly" thousands of instances.  Maybe=
 putting it in Voice
> terms might make it more relevant to that specific working group, if I'm =
trying to model the state
> of ten thousand simultaneous conversations, I'd start to care whether or =
not I'd would have to
> replicate the entire model or representation of the state machine.
>
<snap/>

My previous post didn't come out right, this "decoupling" is ofcourse
needed in the current implementation, which is why this thread exists
:-)

In terms of feedback to the WG, there are public mailing lists at the
W3C per WG where feedback can be posted, though I doubt they need any
convincing on this aspect. And for better participation, we should
push here on making the ASF a member as well.

-Rahul

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org