Obviously this is not a 'one answer fits all' question and it very much depends on the physical deployment you are aiming for and the charistics of the app. One advantage of using the HTTP session to look after state and using stateless session beans is that it makes it easier to have a cluster of EJB servers at the back end if you want to be able to scale up. I have tended to use this approach when building production systems. Hope that helps. --- Andy Grove Chief Technology Officer Orbware Ltd. ** OrCAS EJB Server now available from http://www.orbware.com ** -----Original Message----- From: Samir <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 22 September 2000 17:25 Subject: HTTPSession+ Stateless Session Beans OR Stateful Session Beans >Hi Guys, > >Whats the criteria of Deciding whether to use HTTPSession with Stateless >Session beans or Stateful Session Beans? One reason for using Stateful >Session bean might be to accomodate multiple channels like Web,WAP phone >etc. Any Other Reasons for using it??? In other words my question is why >would i use a Stateful Session bean if I know that I am accessing my >application only thru the web-- when I know that i can track session using >HTTp and take the advantage of instance pooling in Stateless Session beans?? > >Thanks + Regds > >=========================================================================== >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". > =========================================================================== 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".
