Hi,
during server lifetime, any remote interface to a bean stored within the
server (and the session values are stored within the server, i assume that
only a session id will be transfered via a temporary cookie by orion) should
remain valid - at least for the specified maximum timeout (i'm not sure,
which timeout values can be set for session beans and which are the default
values). So it should work to store this information in a stateful session
bean and to store a reference to this bean in the session. But if it is only
for storing data, i'd prefer a simple class containing the data to add to
the HttpSession - session beans are primarily meant to host complicated
_logic_, not simple data...
Regards,
Jens Stutte
> -----Urspr�ngliche Nachricht-----
> Von: Jennifer Kew [mailto:[EMAIL PROTECTED]]
> Gesendet am: Mittwoch, 23. August 2000 00:52
> An: Orion-Interest
> Betreff: Can HttpSession store stateful SessionBean for future usage?
>
> Hi there,
>
> I am asking a common question related to server side
> programming but not
> specific to Orion:
> Can HttpSession store stateful SessionBean for future usage? Is this
> SessionBean still "valid" in the future (for example, browser
> visits next
> time)?
>
> This question arises for the following consideration:
> normally we should
> store some customer's information in the session, for
> example, login or not,
> preferred display language, etc. The problem is, whether we
> should store
> such information directly in the HttpSession, or first at a Stateful
> SessionBean, then store at the HttpSession.
>
> Any hints regarding this question will be highly appreciated!
>
> Thanks,
>
> Jennifer
> ______________________________________________________________
> __________
> Get Your Private, Free E-mail from MSN Hotmail at
> http://www.hotmail.com
>
>
