Session management without SFSB for FBN
Neeraja Neeraj
Greenhorn
Posts: 29
posted 9 years ago
Am thinking instead of using stateful session bean why not use the HttpSession for managing user information like the user id etc and entity beans for persisting the users' saved itenaries.
At any time, the selected but not saved itenary will be on the HttpRequest object. Been musing over this for sometime now.
Please let me know if this design is good or am I missing something.
Thanks.
Neeraj.
At any time, the selected but not saved itenary will be on the HttpRequest object. Been musing over this for sometime now.
Please let me know if this design is good or am I missing something.
Thanks.
Neeraj.
Ben Two
Ranch Hand
Posts: 35
posted 9 years ago
Hi Neeraja
My first suggestion is that you'd better not mention the fbn in your questions, but rise your question in an abstract way.
Then for your question, my opinion is you can always handle the session by HTTP session which is popular for most of the web systems, but how do you handle the session between fat client and server? ofcourse if your fat client is going to connect to the web server as well as thin client, HTTP session is ok. But if your fat client directly to ejb tier, you should think about it.In this way I prefer SFSB but I need time to confirm this solution for performance reason.
My first suggestion is that you'd better not mention the fbn in your questions, but rise your question in an abstract way.
Then for your question, my opinion is you can always handle the session by HTTP session which is popular for most of the web systems, but how do you handle the session between fat client and server? ofcourse if your fat client is going to connect to the web server as well as thin client, HTTP session is ok. But if your fat client directly to ejb tier, you should think about it.In this way I prefer SFSB but I need time to confirm this solution for performance reason.
