-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Folks; not sure whether this is too much a tomcat-related question, but at least it relates to Java based web applications so hope someone around here might have an idea on that: While building a Servlet/JSP based intranet application, quite late I realized that somehow just adding new objects / data to the HTTP session, say, is something so easy one makes excessive use once getting acquainted to it. However, thinking about these information being stored somewhere on the server, the idea of performance impacts due to sessions way too large is the next thing to think of. So, to ask: Are there any reasonable "maximum sizes" for HTTP sessions in general and/or objects attached to a session? What is the maximum session size you would accept before considering rewriting large parts of your application to reduce session size, i.e. by introducing a smarter architecture? Is there any actual use in making _general_ statements here, or is this more likely to be application-dependent and a matter of having server hardware built to meet the needs of the application? What do you think? Thanks in advance and bye, Kristian - -- Kristian Rink * http://zimmer428.net * http://flickr.com/photos/z428/ jab: [EMAIL PROTECTED] * icq: 48874445 * fon: ++49 176 2447 2771 "One dreaming alone, it will be only a dream; many dreaming together is the beginning of a new reality." (Hundertwasser) -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iD8DBQFF5UxocxBAPOA1m6wRAvDUAJ9q7P7uMcAPkWN6oWMCy9reBqwk/ACgpWuH p9dw0PGHuEDSmXGFLoBzTk4= =xHjb -----END PGP SIGNATURE-----
