| 6:38 pm on Oct 9, 2000 (gmt 0)|
I serve my banners through CentralAd. My CentralAd reports have matched pretty well w/ Flycast for almost a year now.
| 9:26 am on Oct 10, 2000 (gmt 0)|
When I want to cross check numbers, I run a cache busting counter. Something with a .cgi?xyz form style submission in it where the ?xyz changes on every page. This is the same way cache busting banner servers work.
| 12:56 pm on Oct 10, 2000 (gmt 0)|
>When I want to cross check numbers, I run a cache busting >counter. Something with a .cgi?xyz form style submission >in it where the ?xyz changes on every page. This is the >same way cache busting banner servers work.
Brett, I have read that three times and I can honestly say I don't understand what it is that you do. Can you give an example or explain a little more? It is the "Something with a ..." sentence that I am having the most trouble with.
| 1:57 pm on Oct 10, 2000 (gmt 0)|
The cache-busting that I use adds a question mark and a random number to the end of the url. That way, the url is seen a unique and the page (or banner) aren't called from cache. Sorry, lousy explaination, but I'm braindead this AM.
I used cache-busting when setting up CentralAd, so perhaps that explains why I've always matched out.
| 2:19 pm on Oct 10, 2000 (gmt 0)|
So, a cgi program can serve a html document (like the one you are reading), or it can redirect the browser to a graphic image.
A url such as:
Will get cached by a browser and not be updated unless they hit refresh.
Will get cached some some, but not all browsers.
Will not get cached by 99% of the browsers if you update that string to reflect the time on each page. Most 'banner buster' urls use a random number. You can update that string from a cgi script if the page is dynamically generated.
You can also do if from simple java script. Drop over to search engine world and look at the source to the page for the banner busting type java script code.
When using an image type counter for this cache busting purposes, you have to have something on your server that can deal with the 'weird url'. Either have the server setup to ignore the extra stuff, or have a cgi banner server program redirect the call to the real image.
I guess after laying it out, I have to agree it is kinda involved to do yourself.