On Thu, 2001-10-25 at 17:03, Geoff Talvola wrote:
> Now that we're talking about future work...
>
> For my use of Webware, a single box is more than enough horsepower. But
> suppose I had to scale up to 2 or more boxes to handle the load and/or for
> redundancy. How would I do it with Webware? For that matter, how is it
> typically done with other systems like IIS with Active Server Pages or Java
> Servlets? Is there some sort of front-end hardware or software that
> distributes the requests evenly to the different web servers?
when using zope (abandoned in favor of webware) we had the same problem.
we solved it by using 4 application server boxes + 1 db box + load
balancer box. the load balancer uses a modified kernel from the linux
virtual server project (http://www.linuxvirtualserver.org/) and balance
the incoming net load by rewriting packet headers. outgoing packets
(already mangled) go directly from the app servers to the client.
> Would Webware support this now, or would it need to be enhanced? The only
> problem area I can think of is session handling. Fortunately, it would be
> easy to write a session store that used a database back-end. Or, without
> too much pain you could modify the adapters so that they always route
> requests for the same session to the same appserver.
sessions were hold on the db, but i think you can very easy write a
DistributedSession class that propagates and cache session data... the
lvs also has a configurable timeout to route incoming connections to the
same server, but with the large number of today masquerated hosts, you
don't usually get anywhere (i.e., one box overloaded, the others almost
idle...)
ciao,
federico
--
Federico Di Gregorio
Debian GNU/Linux Developer & Italian Press Contact [EMAIL PROTECTED]
INIT.D Developer [EMAIL PROTECTED]
Don't dream it. Be it. -- Dr. Frank'n'further
PGP signature
