Watch out for those stateless lawyers... The stateful ones are bad enough!
-----Original Message-----
From: marc fleury [mailto:[EMAIL PROTECTED]]
Sent: Monday, January 22, 2001 7:31 PM
To: jBoss Developer
Subject: RE: [jBoss-Dev] Re: [jBoss-User] jaas
Btw this is rickard's original idea for scalability.
the server stubs are STATELESS, always! :)
The kid is a genius sometimes :) I believe WebLogic is finally going to go
with a full stateless dynamic proxy invocation lawyer in the future :)
marc
|-----Original Message-----
|From: [EMAIL PROTECTED]
|[mailto:[EMAIL PROTECTED]]On Behalf Of Filip Hanik
|Sent: Monday, January 22, 2001 4:27 PM
|To: jBoss Developer
|Subject: Re: [jBoss-Dev] Re: [jBoss-User] jaas
|
|
|gotcha, that helps a lot.
|I'm still learning the code, it will take me a little longer before I can
|make any valuable contributions.
|but don't give up on me :)
|
|Filip
|
|~
|Namaste - I bow to the divine in you.
|~
|Filip Hanik
|Technical Architect
|[EMAIL PROTECTED]
|
|----- Original Message -----
|From: "marc fleury" <[EMAIL PROTECTED]>
|To: "jBoss Developer" <[EMAIL PROTECTED]>
|Sent: Monday, January 22, 2001 4:01 PM
|Subject: RE: [jBoss-Dev] Re: [jBoss-User] jaas
|
|
|JBoss doesn't remember squat. Remeber that we have clients with some logic
|(dynamic proxy invocation handler is a real you can see in our tree) and
|there you have thread extraction of the propagation context. The thread
|doing the call in jboss is associated (actually only when doing the call)
|with the "context information" such as Tx and Principal.
|
|So the client passes on that information and the server uses only for the
|invocation. The bean that is in cache can know whatever you want and we do
|keep transaction association with a given instance (some of our rentrancy
|tests look at that)
|
|marc
|
|
||-----Original Message-----
||From: [EMAIL PROTECTED]
||[mailto:[EMAIL PROTECTED]]On Behalf Of Filip Hanik
||Sent: Monday, January 22, 2001 3:10 PM
||To: jBoss Developer
||Subject: Re: [jBoss-Dev] Re: [jBoss-User] jaas
||
||
||>simple thread association. The thread you use to do your work is
||associated to the security principal you negociated.
||Marc, a simple question,
||
||the thread association lasts during the entire invokation, correct?
||so how does JBoss remember the principal the next time a client does an
||invokation?
||ie, using a thread pool, is one thread always dedicated to that client?
||
||Filip
||
||~
||Namaste - I bow to the divine in you.
||~
||Filip Hanik
||Technical Architect
||[EMAIL PROTECTED]
||
||----- Original Message -----
||From: "marc fleury" <[EMAIL PROTECTED]>
||To: "jBoss Developer" <[EMAIL PROTECTED]>; "Oleg Nitz"
||<[EMAIL PROTECTED]>
||Sent: Monday, January 22, 2001 2:44 PM
||Subject: RE: [jBoss-Dev] Re: [jBoss-User] jaas
||
||
|||I am really interested in find out how JAAS does what it
|||does. I can understand get an instance to a LoginContext
|||and calling a login method but how can all subsequent calls
|||be sent out by that user without being wrapped in some other
|||interface. etc. Seems like there would have to be a security
|||server on the client side?
||
||simple thread association. The thread you use to do your work is
||associated
||to the security principal you negociated.
||
||This is how we do it for transactions as well. Ineficient if you ask me,
||which is why we carry solid association in the MethodInvocation
|(as opposed
||to doing a map lookup everytime with the thread)... The "message" is what
||carries all the contextual information.
||
||marc
||
||
||
|
|
|
