At 17:15 21.08.99 , you wrote:
>Hi Rao,
> Our main problem for not using HttpSession was when we use control-n and
>open a new browser window and try to login as a different user, we get the
>same
>session as the first user.
> So if we store the handle in HttpSession. In the above scenario, second
>user gets the handle of first user. so we have decided to drop the idea of
>using HttpSession and rather implement session management using Stateful
>Session Bean, if we get any help from the mailing list.
>
>Thanx & Regards,
>Sreenivas R.V.
and how are you going to associate the stateful session handle with the
user on each request? using a SFSB doesn't solve that problem for you. if
you really need multiple logical sessions per browser in the same app IMO
it makes most sense you implement that logic on top of HttpSession. maybe
store a hashtable of logical sessions (each associated with an SFSB handle)
there and identify the session you're in with a key that you pass over with
each request). note that you basically have to implement all HttpSession
logic (timeouts etc.) yourself for your logical sessions, so it's worth
reconsidering if you really need to have multiple concurrent sessions from
one browser or if your application design can be modified to not require this.
just my 2c,
robert
(-) Robert Krüger
(-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH
(-) Brüder-Knauß-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
