I knew I was going to get that question... IMHO - I don't like tying myself down to Sessions. One of the nicest things about struts2 was that it got rid of that so I can test easily outside of a web container. Also I have found that 99% of the time I don't even need the session, I need a single Object out of the session, and by using spring injection of session scoped beans I can easily control (during development) the growth of session size. Just too many times have I come onto a project and noone knows what is in the session, and when you look at it the dang thing is so bloated it is silly. (we can discuss how cheap RAM is later :)
Of course YMMV, but I find it easier to "force" developers to become aware of putting something in the session when they have to do it through injection. :) -----Original Message----- From: Dave Newton [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 03, 2008 8:19 AM To: Struts Users Mailing List Subject: RE: session handling --- On Wed, 12/3/08, Fogleson, Allen wrote: > In the case of using Sessions with Struts2 - by the way I > would recommend avoiding this - [...] Why? Dave --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
