|
Hi Cengiz, When you're using
HttpSession you're still using resources. It is more a design issue than
a resource issue. Both HttpSession and STSB are used to keep a conversational
state between a client and application. Depending on your requirements you
should make the decision where to store the state. When you say "just
using HttpSession", you're already making the assumption that
it's a web application and the client is accessing it through the web via
a browser, which is only one of many ways you can access an enterprise
application. Cheers, Dimitar -----Original Message----- Hello List; I wonder why someone would
need to use STSB and undergo a resource usage problem instead of just using
the HttpSession. Is the idea to use your own
session object rather than storing objects under keys in the hashtable?
Regards Cengiz Kayay |
Title: Why store session in Session Bean instead of HttpSession?
- Why store session in Session Bean instead of HttpSession... Cengiz KAYAY
- Re: Why store session in Session Bean instead of Ht... Fei Li
- Re: Why store session in Session Bean instead of Ht... Marco Wang
- Re: Why store session in Session Bean instead of Ht... Milind Kulkarni
- Re: Why store session in Session Bean instead o... Fei Li
- Re: Why store session in Session Bean inste... Dmitri Colebatch
- Re: Why store session in Session Bean instead of Ht... John Harby
- Dimitar Stavrakov
