From owner-freebsd-stable Mon Nov 20 3:30: 9 2000 Delivered-To: freebsd-stable@freebsd.org Received: from sanson.reyes.somos.net (freyes.static.inch.com [216.223.199.224]) by hub.freebsd.org (Postfix) with ESMTP id 8F8B037B479 for ; Mon, 20 Nov 2000 03:30:06 -0800 (PST) Received: from tomasa (tomasa.reyes.somos.net [10.0.0.11]) by sanson.reyes.somos.net (8.9.3/8.9.3) with SMTP id GAA95856; Mon, 20 Nov 2000 06:23:57 -0500 (EST) (envelope-from fran@reyes.somos.net) Message-Id: <200011201123.GAA95856@sanson.reyes.somos.net> From: "Francisco Reyes" To: "stable@FreeBSD.ORG" , "Zero Sum" Date: Mon, 20 Nov 2000 06:27:16 -0500 Reply-To: "Francisco Reyes" X-Mailer: PMMail 2000 Professional (2.10.2010) For Windows 98 (4.10.2222) In-Reply-To: <00112018170204.61849@shalimar.net.au> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Subject: Re: New US CVSup mirrors Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 20 Nov 2000 18:17:02 +1100, Zero Sum wrote: >If you are going to try a second mirror within a short timeframe, it has to >be further up the food chain. > >If the server you select is not available, then an automatic switch to the >next one up the CVS mirror food chain might work. It may still be easier if the servers reported a last update date or some other unique way of identifying last update. The client could use this flag(s) to detect a mirror less up to date than the source tree been updated and display an error which would require some kind of override flag. After a little more thought there is another problem with your approach. It would basically require some server to always be able to indicate the next machine on the "food chain", but what happens when that machine is too busy? In other words that approach simply adds another possible step which may lessen the bottleneck and is more scalable, but is not a distributed approach. IMHO it is best to try to use schemes which distribute the load/tasks as much as possible. francisco Moderator of the Corporate BSD list http://www.egroups.com/group/BSD_Corporate To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message