Business Tier | client state in desktop application- way around Stateful Session Beans?
- by arthur
I read positive inputs on the following posts concerning client state management:
Stateful EJBs in web application?, here, and here.
I want to know how implement such client state management for desktop applications (Swing, AWT, SWT, and other).
let's assume there are n desktop clients supposed to use some (remote) services provided on an Application Server. How to maintain a separate and permanent data state for each client , distinct from the other without have to use using stateful session Beans (SFSB) ? is that even possible on this application type ?
With Webapp(Servlets / JsSF and JSP) some can avoid using SFSB by HttpSession object and/or coupling it with stateless session beans (SLSB). HttpSession object would keep information for each (Web)client separate and the SLSB would play the business logic music.
But HttpSession objects aren't present on desktop application and I go stuck with only SFSB and SLSB. Knowing the problems(Concurrency, Error Handling, usw ) of SFSB, I would have not wanted to use it.
What would be the other options? is there only SFSB available?
Thanks in advances
