From: | "Magnus Hagander" <mha(at)sollentuna(dot)net> |
---|---|
To: | "Greg Sabino Mullane" <greg(at)turnstep(dot)com>, <pgsql-www(at)postgresql(dot)org> |
Subject: | Re: Ads dont connect |
Date: | 2005-10-04 06:58:11 |
Message-ID: | 6BCB9D8A16AC4241919521715F4D8BCE6C7A4A@algol.sollentuna.se |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-www |
> >> 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
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff MacDonald | 2005-10-04 19:46:53 | a bug, the bugs list, and how to break the website search. |
Previous Message | Greg Sabino Mullane | 2005-10-04 02:08:36 | Re: Ads dont connect |