On 8/30/06, THOMAS, JAYANT (SBCSI) <[EMAIL PROTECTED]> wrote:
Ok, Thanks, so basically for each user/session we will have a single instance of the SCXMLExecutor
We'll still need to look at synchronization, though ... it's legal for there to be multiple requests active on the same session, and the likelihood of that increases a lot if you're using AJAX style callbacks. Thanks
Jayant
Craig -----Original Message-----
From: Rahul Akolkar [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 6:45 AM To: Jakarta Commons Users List Subject: Re: Shale + SCXML integration: On 8/29/06, THOMAS, JAYANT (SBCSI) <[EMAIL PROTECTED]> wrote: > Thanks, As you can see SCXMLDialogNavigationHandler is a singleton and > handleNavigation will be accessed by the many users concurrently. if we > use servlet context to store the SCXMLExecutor, we have single > instance for all the users so the implementation itself will have > issues, so which ever framework we use the scxml executor will have > issues unless we create a new instance for each request or model the > SCXMLExecutor itself as a controller , <snip/> Not ServletContext (there is no such thing, there is an abstracted out ExternalContext) -- but the session map (in that example). > also iam not sure why the > SCXMLExecutor is not thread safe ??., we cannot use synchronize blocks > in a servlet request since it will block all the request. > > It will be nice if we can implement the SCXMLExcector as part of the > Shale framework itself. <snap/> I agree. -Rahul > Thanks > Jayant <snip/> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
