I was wondering if anyone could share their thoughts how to handle sessions (login etc) from mainly the Travel Agent (swing)?
I have been trying to restrict usage of sessionbeans for performance reasons. I currently only one sessionbean which is the shoppingcart (to store the segments).
I also had an idea: When searching for flight, I wanted to store the result(s) in the HTTPSession (thus pushing flight data out to the webservers).
How do I handle login from the swing client? Let the swing app. handle security with login (easy to bypass)While logging in to swing app. the app. server can verify the login details and give the swing client a uniq id. Everytime the swing app calls a method, this ID is sent as part of the paramters. This ID will have a timeout.Use a sessionfacade for all clients (web and swing) and thereby use more resourcesAny other suggestions?
Any suggestions are very welcome!
Thanks in advance for replying
[ October 10, 2005: Message edited by: Trond Hjelmaas ]