Alex,
Something that I meant to post, and was reminded of in the mods forum, is a page_id.
Because banner rotations require a unique ID, usually numerical, Links should have the internal ability to generate and increment a "page_id" every time it writes out a page.
This way, a 'random' and 'unique' number is passed to the banner advertising, and for people who need multiple banners they can just append a 1,2... to the uses in their HTML.
But, rather than making people do all sorts of hurdles, creating a global variable that is used for _build_ and for any CGI call, and which is incremented by each of the 'write' routines in the program, would solve many, many problems.
I'm sure you see what I'm saying. Search and other dynamic cgi programs can initialize and access the variable (say, with the time) just as any other routine can, so it simply becomes a 'unique' identifier that is different, and incremented each time a page is printed, saved, or returned.
Something that I meant to post, and was reminded of in the mods forum, is a page_id.
Because banner rotations require a unique ID, usually numerical, Links should have the internal ability to generate and increment a "page_id" every time it writes out a page.
This way, a 'random' and 'unique' number is passed to the banner advertising, and for people who need multiple banners they can just append a 1,2... to the uses in their HTML.
But, rather than making people do all sorts of hurdles, creating a global variable that is used for _build_ and for any CGI call, and which is incremented by each of the 'write' routines in the program, would solve many, many problems.
I'm sure you see what I'm saying. Search and other dynamic cgi programs can initialize and access the variable (say, with the time) just as any other routine can, so it simply becomes a 'unique' identifier that is different, and incremented each time a page is printed, saved, or returned.