Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 513 invoked by uid 500); 29 Feb 2000 04:35:44 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 494 invoked from network); 29 Feb 2000 04:35:44 -0000 From: "William A. Rowe, Jr." To: Subject: Mirror site discussion - another thought... Date: Mon, 28 Feb 2000 22:35:41 -0600 Message-ID: <000201bf826e$70896850$345985d0@corecomm.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <20000228235835.B15172@indigo.ie> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N I just tossed out a 1.3.12 notice in the windows forum for the Win32 binaries availablity, and wanted to note how the mirror sites reflect the path specs. I noticed that http://dolemite.toronto.com/apache/dist/binaries/win32/ is so far out of date that it doesn't include the 1.3.11 build. Not picking on this one mirror, but would it make sense to run a bot periodically against our 'proscribed' list of mirrors, and single out those that are > one week/month/year out of date? Bill pps obviously some push-pull mechanism will alievate some of this, tho not all mirror operators may be willing to use such a method.