Ken, Over the year or so I've been subscribed to this list, I've seen discussions (and read referenced articles) suggesting web servers such as Tomcat do well for moderate traffic as long as the Session Scope contains less than 1k of data. Putting 2 integers into Session scope doesn't sound like it should cause much of a performance issue unless you have an incredibly HIGH volume of peak traffic. However, if you ask the list about session scope/cache issues for your particular java web server, perhaps people will confirm or deny this. :)
Regards, David -----Original Message----- From: Keng Onn [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 29, 2005 5:45 AM To: user@struts.apache.org Subject: RE: user Digest 24 Mar 2005 14:53:20 -0000 Issue 5708 Thanks for the advice, David :)! But isn't it more troublesome (coz I gotta manually remove it afterwards :P) / memory intensive to store variables in session scope instead of request scope? Coz I thought (from reading somewhere on the Internet) that we should generally restrict the scope as much as we can, as a form of best practice. Regards, Keng Onn. === Orig Message === Subject: RE: user Digest 24 Mar 2005 14:53:20 -0000 Issue 5708 From: "David G. Friedman" <[EMAIL PROTECTED]> Date: Sun, 27 Mar 2005 23:24:08 -0500 To: "Struts Users Mailing List" <user@struts.apache.org> Keng Onn, If you just want the "groupId" and "action" variables, you could always put them in session scope, perform a forward with redirect="true", then read the groupId and action from the session scope in the new action. Just be sure to remove those variables from session scope IF you don't need them anymore. Regards, David, an Caucasian with an English name :) --------------------------------------------------------------------- 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]
