Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: Re: New site - minor problem
Date: Mon, 6 Dec 2004 12:32:53 -0000
Message-ID: 
 <E7F85A1B5FF8D44C8A1AF6885BC9A0E4527CF9@ratbert.vale-housing.co.uk>
Thread-Topic: [pgsql-www] New site - minor problem
Thread-Index: AcTbhd5zSOpgJ4FyTXSuuV7uq1rJ5AACTakw
From: "Dave Page" <dpage@vale-housing.co.uk>
To: "Alexey Borzov" <borz_off@cs.msu.su>
Cc: <pgsql-www@postgresql.org>

=20

> -----Original Message-----
> From: Alexey Borzov [mailto:borz_off@cs.msu.su]=20
> Sent: 06 December 2004 11:22
> To: Dave Page
> Cc: pgsql-www@postgresql.org
> Subject: Re: [pgsql-www] New site - minor problem
>=20
> If you have problems with directing traffic to your server,=20
> then we'll probably need to find "real" hosting. Because=20
> we'll still need to direct all form submissions to your=20
> server (uncluding voting in surveys).

The form submissions will not be a problem as they are a minimal amount
of traffic. Handling tens or hundreds of thousands of hits per day for
mirrors is a lot more. The box I'm using is on a 2Mb leased line (which
costs an arm and a leg here btw). If the traffic impacts our normal
business in any way, it will have to be removed - hence I'm being
cautious.

> A major objection to mirroring the lists of mirrors is that=20
> we risk having a stale mirror having a list of even more=20
> stale (and non-working) mirrors.

That happens quite rarely, and even when it does, 99% of users will
simply choose another mirror. This is also how it is setup now...

/D