I'm aware that the developers USING struts have to be careful about how much they put into session. We can control this. What I'm concerned about is how much struts might be doing on its own, such as storing the locale. A few things stored in session is ok, especially if they don't change with every request, etc.. However, large amounts (size and/or numbers of objects) of data will significantly reduce scalability in a failover system due to the fact that the session (or rather any 'new' data in the session) must be serialized with every request.
Primitives such as Strings are good too since they're immutable. If the struts framework is storing things such as a hashmap, this too may cause a problem since the container will not know when to serialize the hashmap unless the map is handled in an 'immutable' fashion. Annnnd, since you brought it up.. we will be using a server farm.. what's the issue you mentioned? Is it particular to tomcat? Thanks Mark, George ----- Message from Mark Lowe <[EMAIL PROTECTED]> on Wed, 8 Jan 2003 10:49:44 +0100 ----- How many "things" you put in the session is up to you.. You basically make strutures (arrays, maps and such forth) available to your presentation layer by putting into the session, request or application scope depending on what your "things" have to do.. Issues relating to session will have more to do with the servlet container than struts itself, The only issue i'm aware of with sessions in tomcat for example is that there can be issues if you've a server farm.. The decision of what to put in the session or in the request is down to whoever designs the system. Hope this helps mark p.s . If anyone knows about the issue of sessions and farms i'd be glad to hear from anyone who's solved this. Mercoled�, 8 gen 2003, alle 10:32 Europe/Rome, [EMAIL PROTECTED] ha scritto: > I'm a newb to struts, investigating it as a replacement to our > home-grown > framework. The big issues we're dealing with are scalability and > fail-over > support. The combination of the two issues require that the session > size > and number of objects remain small (and generally immutable) for > serialization performance issues. > > My question is 'How much is the struts framework using the session'? > I've > done a little investigation with some sample example applications and > found > it's storing only the locale. I know it could also be storing Tokens, > but > only on demand eh? Do heavier apps or certain functions of struts use > the > session heavily? > > Thanks! > > -George -- "NOTICE: The information contained in this electronic mail transmission is intended by Convergys Corporation for the use of the named individual or entity to which it is directed and may contain information that is privileged or otherwise confidential. If you have received this electronic mail transmission in error, please delete it from your system without copying or forwarding it, and notify the sender of the error by reply email or by telephone (collect), so that the sender's address records can be corrected." -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
