RE: Can HttpSession store stateful SessionBean for future usage?

2000-08-26 Thread Joe Stewart

Mike,

Could you provide a code snippet showing how you do this?

Joe

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike
Cannon-Brookes
Sent: Friday, August 25, 2000 10:31 PM
To: Orion-Interest
Subject: RE: Can HttpSession store stateful SessionBean for future
usage?


Jason,

I believe if you just throw the whole session bean into the session, Orion
will only serialise the handle anyway - it's real smart about that ;)

Mike


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jason A.
 Westra
 Sent: Saturday, 26 August 2000 12:34
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Hi Mike!  I recommend storing the handle to the session bean
 rather than the
 session bean itself.  Handles are guaranteed to be serializable and are
 generally smaller, which ensures persistence of the Http session
 (if the web
 container choses to do so) will be successful and faster.

 Jason

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
 Cannon-Brookes
 Sent: Wednesday, August 23, 2000 3:59 AM
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Sure, this is the normal way that SSB's are stored for web
 clients, binding
 it in the session.

 Mike

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jennifer Kew
 Sent: Wednesday, August 23, 2000 8:52 AM
 To: Orion-Interest
 Subject: 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













RE: Can HttpSession store stateful SessionBean for future usage?

2000-08-26 Thread Mike Cannon-Brookes

Not sure a snippet is really needed - it's just like putting any other
object in the session? Orion takes care of all the serialisation for you.

% session.put("thebean", mysessionbean); %

Mike

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Stewart
 Sent: Saturday, 26 August 2000 7:33
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Mike,

   Could you provide a code snippet showing how you do this?

 Joe

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
 Cannon-Brookes
 Sent: Friday, August 25, 2000 10:31 PM
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Jason,

 I believe if you just throw the whole session bean into the session, Orion
 will only serialise the handle anyway - it's real smart about that ;)

 Mike


  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Jason A.
  Westra
  Sent: Saturday, 26 August 2000 12:34
  To: Orion-Interest
  Subject: RE: Can HttpSession store stateful SessionBean for future
  usage?
 
 
  Hi Mike!  I recommend storing the handle to the session bean
  rather than the
  session bean itself.  Handles are guaranteed to be serializable and are
  generally smaller, which ensures persistence of the Http session
  (if the web
  container choses to do so) will be successful and faster.
 
  Jason
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
  Cannon-Brookes
  Sent: Wednesday, August 23, 2000 3:59 AM
  To: Orion-Interest
  Subject: RE: Can HttpSession store stateful SessionBean for future
  usage?
 
 
  Sure, this is the normal way that SSB's are stored for web
  clients, binding
  it in the session.
 
  Mike
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Jennifer Kew
  Sent: Wednesday, August 23, 2000 8:52 AM
  To: Orion-Interest
  Subject: 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
 
 
 
 
 
 









RE: Can HttpSession store stateful SessionBean for future usage?

2000-08-26 Thread Robert Nicholson

If the session been is passivated does it transparently unpassivate itself
when he uses the handle again?

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jason A.
 Westra
 Sent: Friday, August 25, 2000 7:34 PM
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Hi Mike!  I recommend storing the handle to the session bean
 rather than the
 session bean itself.  Handles are guaranteed to be serializable and are
 generally smaller, which ensures persistence of the Http session
 (if the web
 container choses to do so) will be successful and faster.

 Jason

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
 Cannon-Brookes
 Sent: Wednesday, August 23, 2000 3:59 AM
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Sure, this is the normal way that SSB's are stored for web
 clients, binding
 it in the session.

 Mike

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jennifer Kew
 Sent: Wednesday, August 23, 2000 8:52 AM
 To: Orion-Interest
 Subject: 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










RE: Can HttpSession store stateful SessionBean for future usage?

2000-08-26 Thread Robert Nicholson

Hi, he's not guarantteed to keep the reference is he?

Will the server passivate if he's put the beans remote reference in the
session?

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
 Cannon-Brookes
 Sent: Saturday, August 26, 2000 11:04 AM
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Not sure a snippet is really needed - it's just like putting any other
 object in the session? Orion takes care of all the serialisation for you.

 % session.put("thebean", mysessionbean); %

 Mike

  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Joe Stewart
  Sent: Saturday, 26 August 2000 7:33
  To: Orion-Interest
  Subject: RE: Can HttpSession store stateful SessionBean for future
  usage?
 
 
  Mike,
 
  Could you provide a code snippet showing how you do this?
 
  Joe
 
  -Original Message-
  From: [EMAIL PROTECTED]
  [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
  Cannon-Brookes
  Sent: Friday, August 25, 2000 10:31 PM
  To: Orion-Interest
  Subject: RE: Can HttpSession store stateful SessionBean for future
  usage?
 
 
  Jason,
 
  I believe if you just throw the whole session bean into the
 session, Orion
  will only serialise the handle anyway - it's real smart about that ;)
 
  Mike
 
 
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of Jason A.
   Westra
   Sent: Saturday, 26 August 2000 12:34
   To: Orion-Interest
   Subject: RE: Can HttpSession store stateful SessionBean for future
   usage?
  
  
   Hi Mike!  I recommend storing the handle to the session bean
   rather than the
   session bean itself.  Handles are guaranteed to be
 serializable and are
   generally smaller, which ensures persistence of the Http session
   (if the web
   container choses to do so) will be successful and faster.
  
   Jason
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
   Cannon-Brookes
   Sent: Wednesday, August 23, 2000 3:59 AM
   To: Orion-Interest
   Subject: RE: Can HttpSession store stateful SessionBean for future
   usage?
  
  
   Sure, this is the normal way that SSB's are stored for web
   clients, binding
   it in the session.
  
   Mike
  
   -Original Message-
   From: [EMAIL PROTECTED]
   [mailto:[EMAIL PROTECTED]]On Behalf Of Jennifer Kew
   Sent: Wednesday, August 23, 2000 8:52 AM
   To: Orion-Interest
   Subject: 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
  
  
  
  
  
  
 
 
 
 







RE: Can HttpSession store stateful SessionBean for future usage?

2000-08-25 Thread Jason A. Westra

Hi Mike!  I recommend storing the handle to the session bean rather than the
session bean itself.  Handles are guaranteed to be serializable and are
generally smaller, which ensures persistence of the Http session (if the web
container choses to do so) will be successful and faster.

Jason

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Mike
Cannon-Brookes
Sent: Wednesday, August 23, 2000 3:59 AM
To: Orion-Interest
Subject: RE: Can HttpSession store stateful SessionBean for future
usage?


Sure, this is the normal way that SSB's are stored for web clients, binding
it in the session.

Mike

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jennifer Kew
Sent: Wednesday, August 23, 2000 8:52 AM
To: Orion-Interest
Subject: 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








RE: Can HttpSession store stateful SessionBean for future usage?

2000-08-25 Thread Mike Cannon-Brookes

Jason,

I believe if you just throw the whole session bean into the session, Orion
will only serialise the handle anyway - it's real smart about that ;)

Mike


 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jason A.
 Westra
 Sent: Saturday, 26 August 2000 12:34
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Hi Mike!  I recommend storing the handle to the session bean
 rather than the
 session bean itself.  Handles are guaranteed to be serializable and are
 generally smaller, which ensures persistence of the Http session
 (if the web
 container choses to do so) will be successful and faster.

 Jason

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Mike
 Cannon-Brookes
 Sent: Wednesday, August 23, 2000 3:59 AM
 To: Orion-Interest
 Subject: RE: Can HttpSession store stateful SessionBean for future
 usage?


 Sure, this is the normal way that SSB's are stored for web
 clients, binding
 it in the session.

 Mike

 -Original Message-
 From: [EMAIL PROTECTED]
 [mailto:[EMAIL PROTECTED]]On Behalf Of Jennifer Kew
 Sent: Wednesday, August 23, 2000 8:52 AM
 To: Orion-Interest
 Subject: 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











Re: Can HttpSession store stateful SessionBean for future usage?

2000-08-23 Thread Vlad Petric

 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)?

A SessionBean can be stored in a HTTPSesion, however, my advice would be to
store the handle of the SessionBean (which is also Serializable).

Vlad






RE: Can HttpSession store stateful SessionBean for future usage?

2000-08-23 Thread Harry Hendrata



Hi,

Could you use cookies? e.g. you can use the cookies as key to getting your
user's profile

regards,

harry

-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Jennifer Kew
Sent: Wednesday, August 23, 2000 6:52 AM
To: Orion-Interest
Subject: 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