Mailing-List: contact commons-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Users List" <commons-user@jakarta.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Reply-To: <mike@goomzee.com>
From: "Mike Sparr - www.goomzee.com" <mike@goomzee.com>
To: "'Jakarta Commons Users List'" <commons-user@jakarta.apache.org>
Subject: RE: [SCXML] Concurrent users
Date: Tue, 13 Dec 2005 03:25:17 -0700
Organization: GOOMZEE.COM
Message-ID: <032c01c5ffcf$83f594b0$3daffea9@MSPARR>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit
Importance: Normal
In-Reply-To: <02f501c5ff9d$06fbc9c0$3daffea9@MSPARR>

Rahul,

I think build may have broke due to dependency on XercesImpl, xml-apis,
and possibly xalan jar dependencies.  Your recent code change likely
requires them now so you may update the dependencies and jars to your
build.xml, plus the docs.  Also, we noticed that the context vars return
null within onentry and can only be retrieved during ontransition.  I'm
not sure if just our implementation or how it's built.  Anyhow, just a
little input from our findings.

Rgds,

Mike


-----Original Message-----
From: Mike Sparr - www.goomzee.com [mailto:mike@goomzee.com] 
Sent: Monday, December 12, 2005 9:24 PM
To: 'Jakarta Commons Users List'
Subject: [SCXML] Concurrent users


Rahul,

Your code worked (from your personal snapshot) fine - thanks.  One issue
we're now facing is handling concurrent users from multiple clients.  My
goal is to use one scxml doc to manage app flow for all users.  It looks
like there is one context and it's shared, so if we trigger an event, it
will affect any user.  We have created a HashMap (in memory) to store
key/handle to client for sending response, but are having troubles
dealing with concurrent users and their state.

For example:

Web request (state 1, event 3)
IM request (state 2, event 1)

Can the engine handle that or do you know how best to implement?  My
thought was to store state and last event per user, then navigate to
that somehow for their requests.  I assume there must be a better way?

Thanks,


Mike


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


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