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