From owner-freebsd-isp Tue Jun 29 20: 9:45 1999 Delivered-To: freebsd-isp@freebsd.org Received: from phoenix (phoenix.aye.net [206.185.8.134]) by hub.freebsd.org (Postfix) with SMTP id 525D8154A5 for ; Tue, 29 Jun 1999 20:09:41 -0700 (PDT) (envelope-from barrett@phoenix.aye.net) Received: (qmail 9125 invoked by uid 1000); 30 Jun 1999 03:07:39 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 30 Jun 1999 03:07:39 -0000 Date: Tue, 29 Jun 1999 23:07:39 -0400 (EDT) From: Barrett Richardson To: Francisco Reyes Cc: "Russell L. Carter" , "freebsd-isp@FreeBSD.ORG" Subject: Re: Redundant Remote Webserver clustering In-Reply-To: <199906300232.WAA29760@arutam.inch.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 29 Jun 1999, Francisco Reyes wrote: > On Tue, 29 Jun 1999 19:00:50 -0700, Russell L. Carter wrote: > > >%> Define clustering. If you mean a bunch of boxes that serve up HTTP > >%> requests and the lot of them continue working in the face of a > >%> failure on one > > Just recently found http://www.eddieware.org > It is a research project for DNS and HTTP load balancing. > > Check out the ACE Director at www.alteon.com. You give the switch the IP address of your website, plug each of your servers into a different port. The switch relays and balances the port 80 traffic to itself across the servers. I use a similar concept with a different alteon swith to do transparant HTTP cacheing. Work great. If the cache server goes down, the switch detects it instantaneously (in human terms) and our users never know (except that the absence of the cache server makes surfing slower). Works great. - Barrett > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-isp" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message