>I'm writing a fairly large JSP-based application (using model 2 which,
>incidentally, I think is terriffic). Thus far, I've shied away from <USEBEAN
>... LIFESPAN="session"> because our application must be able to scale to use
>multiple webservers. Unfortunately, this means that all of my beans, when
>they need session information, must talk to our application server in
>another VM. Obnoxious. What I'm wondering is:
>
>Does there exist now, or are there plans for a mechanism by which
>LIFESPAN="session" will work across multiple webservers? Also, is there
>anybody else out there who is dealing with a similar situation, and if so,
>how?
The implementation of session is not defined by either the Servlet API or
the JSP specification, so the question is not so much relvant to JSP as to
the environment in which you are using it. An application server may or
may not distribute session information across multiple machines, or it may
be configurable. My impression is that most commercial application servers
now support distributed sessions to some degree.
Of course, if you are planning on using distributed session management,
there will be some design considerations. Weblogic distributes sessions by
serializing them and putting them in a database, which of course can
quickly become a scalability problem in its own right. Netscape
Application Server exchanges session "heartbeats" between its various
nodes, which seems a little better, but they recommend making the sessions
as small as possible (5k or less).
Those are the two I know something about. My general rule is to try to
minimize the amount of data stored in the session, and to try to update
that data as infrequently as possible.
Hope that's of some use.
-Ben
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff JSP-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
