I second the suggestion to use Witango to rotate the banners. It'd make everything
simpler - development, imnplementation, logging, etc. It'd also be a great way to
learn the ins & outs of Witango
I use the @RANDOM tag to display random header images like this:
<img src=/wide/<@RANDOM LOW=1 HIGH=@@Domain$WideNumber>.jpg WIDTH=484 HEIGHT=68
BORDER=0 ALIGN=top>
There's nothing particularly clever about this - except that the HIGH number (in other
words the number of Random images) is held in a Domain Scope variable. As this randow
header code appears in 50 or 60 TAFs, changing the number of images would be a big job
- so I store the number in a variable that can easily be changed site-wide
To me this is classic Witango elegance and you'd lose this kind of integration by
using another advert rotation scheme
Of course you can also <@INCLUDE> Witango variables into poages - and these might
contain Nav bars, sidebars, logos, etc
>You will need to use the @URL tag rather than the
>@include tag. The web server will only process one
>cgi program per page. That cgi program would be
>Witango in this case. It would ignore your mgi code.
>
>However, the @URL tag would work fine but be a
>little slower since it has to resolve the URL twice
>per page. An alternative would be to use Witango
>to rotate your banners. :)
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
