On Wednesday, April 14, 1999 03:34, Chris Fesler [SMTP:[EMAIL PROTECTED]] wrote: > 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? For scalability one could use a mechanism that works on a lower level: distribute incoming HTTP requests over a pool of WWW servers (creating a single virtual WWW server), but ensure that each client (within a period of time) will always be redirected towards the same physical WWW server. A device that does this is Cisco's local director, a kind of networking switch that hides multiple physical devices behind a virtual host,port transport endpoint. There are also (other) software solutions for such things, like reverse HTTP proxies. An example is Netscape's proxy server when used in "reverse mode". =========================================================================== 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".
