commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mike Stanley" <mstan...@cauldronsolutions.com>
Subject RE: [General] New sandbox component idea
Date Thu, 13 Nov 2003 18:45:10 GMT
Rules based load balancer?  Seems to me like this could need a load balancer
of its own.  Have you stress tested it?  I'm not saying it can't be useful
as a smart (policy based) redirector, but as a thin large scale load
balancer the Servlet lifecycle may be a little heavier than necessary.  Can
you give an example in which this serves as a better "load balancer" than
other alternatives?

- Mike

> -----Original Message-----
> From: Shapira, Yoav [mailto:Yoav.Shapira@mpi.com]
> Sent: Thursday, November 13, 2003 1:33 PM
> To: Jakarta Commons Developers List
> Subject: RE: [General] New sandbox component idea
>
>
>
> Howdy,
>
> >> Yup, and I use them.  This is a bit different, in two ways:
> >> - pure servlet container, since there's nothing tomcat-specific
> >
> >How are you handling session affinity and/or migration?
>
> A simple way: the same rule will always redirect to the same server.  So
> if the load balancer's administrator changes the rules while a user is
> using the system, and the app depends on session stuff, the user is
> screwed.
>
> >That aspect would seem to be something to discuss with Filip.  I think
> that
> >it would be useful to add that concept to the Tomcat work.
>
> Maybe: discussion can't hurt, which I why I brought this up ;)  I've
> taken care to make my stuff portable to other servlet containers, not
> just tomcat, so I don't want to tie it tightly into tomcat.
>
> BTW, to your list of other web components for perhaps a WebApp Commons,
> I would maybe add some things from the log4j-sandbox that I've been
> working on.  There are servlets there that I hope will some day grow
> into a log4j administration webapp.
>
> Yoav Shapira
>
>
>
> This e-mail, including any attachments, is a confidential
> business communication, and may contain information that is
> confidential, proprietary and/or privileged.  This e-mail is
> intended only for the individual(s) to whom it is addressed, and
> may not be saved, copied, printed, disclosed or used by anyone
> else.  If you are not the(an) intended recipient, please
> immediately delete this e-mail from your computer system and
> notify the sender.  Thank you.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: commons-dev-help@jakarta.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message