We are using HttpSession frequently in our application. I have a situation where I wanted to use session more efficiently. For e.g. on first page user selected an item, I put that in session. On next page user selects some other item, which I am attaching to first one and so forth have couple of more pages. Now if user clicks "back" and "forward" browser buttons several times (sometimes with new values in sesssion by changing some params and clicking done on the page) sometimes w/o changing anything click on "forward" of browser. Things look screw after these activities.
Is there a better way to handle Session? I plan to look into EHCache (that's what hibernate uses) to replace HttpSession. Do you think it's a good idea but for now I will have to deal with session atleat for first release of the application, which is next week. Any ideas.