both concepts are applicable in that
scoping of session based information should ultimately pull from
user-neutral entity (such as Class Object) whose end of life is not
dependent on either client session passivation or client session termination
Any underlying synchronisation mechanisms for entities (synchronised
objects) are entirely dependent on selection of scope and
whether the implementor is controlling the object via declarative or
programmatically means
Here are some good reads
Problem Scenario for Stateful Session Beans
http://docs.sun.com/source/817-2162-10/bpstatement.html
Software Architecture in Practice: The Luther Architecture
http://www.awprofessional.com/articles/article.asp?p=32063&seqNum=3
HTH,
Martin-
----- Original Message -----
From: "Dave Newton" <[EMAIL PROTECTED]>
To: "Struts Users Mailing List" <user@struts.apache.org>
Sent: Thursday, June 09, 2005 1:47 PM
Subject: Re: Multiple user - problem
Martin Gainty wrote:
-synchronisation of all method calls
Why all? (Really, why _any_, since you can synchornized any shared data
structures.)
-scoping of data entities(assuming you are implementing with beans)
Unless he's storing user data in application scope, this shouldn't be an
issue, should it?
Dave
---------------------------------------------------------------------
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]
