Hi David,
Thanks for jumping back in.
Here are the original 4 options that you posted (I numbered them for
reference);
(1)- one session id per client vm
(2)- one session id per client connection
(3)- one session id per login (security scoped)
(4)- one session id per remote ejb proxy
I prefer 4 because it will work best with what I expect to be the
most typical use case (but I could be wrong so please point out
better info if I am). Typical being a web app connected to the ejb
tier. Although 3 is probably close enough to 4 that it would not
cause conflict in the items in the cache being locked. I think both 1
and 2 would cause lots of conflict in what is being locked.
Now I'm full of questions :-)
What are the motivations/benifits/costs WRT the current openejb code
base WRT the 4 options?
Do you have a preference one way or the other? (as was said earlier
less code change is better, at least in the beginning :)
How is the sessionid concept currently implemented (if at all)?
TTFN,
-bd-
On Jul 14, 2006, at 4:43 PM, David Blevins wrote:
The question hasn't been answered at a concrete level I was looking
for. To play along... the session id is tied to the "client",
fine. What is a client and how do we identify one? ;)
-David
On Jul 12, 2006, at 8:56 AM, Jeff Genender wrote:
Ok...then I think we are in agreement then here ;-)
Bill Dudney wrote:
Hi Jeff,
That might be the current impl. But this whold thread was to
discuss what the session id should be.
I'm trying to say that of the 4 options presented at the root of
this thread I'd prefer that the session ID be tied to the
particular client which would lead to the smallest glob of stuff
that gets locked.
if we go with the first option (again from the root of the
thread) we would have a session id per client vm, that is what I
don't want.
-bd-
On Wednesday, July 12, 2006, at 11:36AM, Jeff Genender
<[EMAIL PROTECTED]> wrote:
Bill Dudney wrote:
If the seesion id is tied to the client vm, i.e. the web vm
then there is one session id per web tier vm (which in all
likelyhood has many many users).
Hmmm...I don't think I agree here. I believe the session id is
tied to
the client...period. There is one id per session per
client...not web
tier vm. Maybe you can explain what you are thinking?
Its my understanding the session id is like a web session...that
particular client gets a unique id that represents only that
session for
that client.
Jeff
