Comments on: State Management with the Http Session http://jaybose.com/archives/state-management-with-the-http-session/ Yapping about stuff. Fri, 10 Sep 2010 19:10:26 +0000 http://wordpress.org/?v=2.2.2 By: Stephen Colebourne http://jaybose.com/archives/state-management-with-the-http-session/#comment-28 Stephen Colebourne Mon, 08 Aug 2005 12:26:00 +0000 http://jaybose.com/archives/state-management-with-the-http-session/#comment-28 2K! We have 200K+ and it works just fine. It partly depends on what kind of site you are running. Of course Brown and Botzum are from IBM, a company that wants to sell you a very expensive product to handle session issues like this. So, perhaps I'll take their advice with a pinch of salt... 2K! We have 200K+ and it works just fine. It partly depends on what kind of site you are running.

Of course Brown and Botzum are from IBM, a company that wants to sell you a very expensive product to handle session issues like this. So, perhaps I’ll take their advice with a pinch of salt…

]]> By: jaybose http://jaybose.com/archives/state-management-with-the-http-session/#comment-6 jaybose Mon, 04 Jul 2005 19:02:27 +0000 http://jaybose.com/archives/state-management-with-the-http-session/#comment-6 I actually do talk about garbage collection. I actually do talk about garbage collection.

]]> By: Brian http://jaybose.com/archives/state-management-with-the-http-session/#comment-4 Brian Sun, 03 Jul 2005 17:17:42 +0000 http://jaybose.com/archives/state-management-with-the-http-session/#comment-4 In the past we used HttpRequest to store data that would not be needed past the current request. This allowed us to dispose of unneeded data in a timely fashion. I do not know if you can do the same with webwork or struts. You can access the request in webwork but can not place items into it. The point you're missing is garbage collection. Object creation and destruction are the two most expenseive operations in java. if you keep everything is session and use wait for the session to time out to have these items removed you could be placing a lot of information in session that could be destroyed all at once. In the past we used HttpRequest to store data that would not be needed past the current request. This allowed us to dispose of unneeded data in a timely fashion. I do not know if you can do the same with webwork or struts. You can access the request in webwork but can not place items into it.

The point you’re missing is garbage collection. Object creation and destruction are the two most expenseive operations in java. if you keep everything is session and use wait for the session to time out to have these items removed you could be placing a lot of information in session that could be destroyed all at once.

]]>