I decided to store the session state in the Application tier because I have two different clients (Web, Swing).
I have just basics problems I can't get rid of.
After having shown the flight availability to the client, the client can selects or not flights:
- Should the client send me back the selected flights and then I build the value object that represents this selection before sending it to the application tier. - Or before sending him the flight list, I keep all of them in the application tier SFSB and I just retrieve them in next requests.
I know that keeping all the flights could consume memory but in case of if the client hasn't selected any flights, I must get all the flights with a departure/return time with +/- 1 hour and price them. In that latter case I must also keep the search values in the session.
So, I'm a bit confused if I weither or not use the Session to store flight availabilities.