Hello, We are building a struts based web application bit like a shopping cart.
Right now the application is in its initial stages so it has to support few users hence we are storing user information in http session. But eventually application has to be scalable to support thousands of online users in a glass fish cluster. Hence the session storage is not scalable, I thought of using a database for user activity and deleting the rows when user logs out. But i can see my performance is getting hit by this approach. I need a architecture help on this problem. can somebody help me on this ? thank you. -- View this message in context: http://www.nabble.com/Temporary-user-activity-information-storage-problem....-tp22772603p22772603.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org