Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable
Subject: Re: Ads dont connect
Date: Tue, 4 Oct 2005 08:58:11 +0200
Message-ID: <6BCB9D8A16AC4241919521715F4D8BCE6C7A4A@algol.sollentuna.se>
Thread-Topic: [pgsql-www] Ads dont connect
Thread-Index: AcXIiLDfi+XD93dGRHG6APNlrpQaoAAJyUGw
From: "Magnus Hagander" <mha@sollentuna.net>
To: "Greg Sabino Mullane" <greg@turnstep.com>,
	<pgsql-www@postgresql.org>

> >> Although ads.postgresql.org could in theory also track the=20
> IPs that=20
> >> they send the image too and try and match that way if the=20
> cookie was=20
> >> not found. That should fix it 99% of the time, I would think.
>  =20
> > Except then it has to save the IPs for every hit to every page *in=20
> > case* someone happens to click through ...
>  =20
> But aren't they already saved in the apache logs? It would be=20
> expensive to parse them, true, but this would be a rare case=20
> for those who are not accepting cookies. Or at the very=20
> least, what if the non-mirror site (e.g. www.postgresql.org)=20
> used a slightly different system that did not rely on the=20
> cookie/image scheme?

Can't talk about the ads.pg server, but al the static servers have
logging turned off to handle the performance requirements.

And what do you mean with the "non-mirror site www.postgresql.org"?
www.postgresql.org is the mirrored site ;-)

//Magnus