Good point, Robert .... always thinking ..
Ian
-----Original Message-----
From: Robert Shubert
Just an interesting note:
The HASH function of T2K restricts output to 32 characters and it is
therefore possible to create two identical HASHes with <@CIPHER
action=hash str=<@CURRENTTIME>>.
Another way of creating an ever increasing value is <@TSTOSECS
<@CURRENTTIMESTAMP>><@TIMER> This value is ensured to be unique unless
the same person is able to retrieve two pages in the same millisecond.
Keep in mind that this only works if the CURRENTTIMESTAMP is ever
increasing, if you adjust the time on the server (or adjust for daylight
savings) it could create duplication, although it's still highly
unlikely.
Bob Shubert
Tronics
> Ian Daniel wrote:
>
> Hey Garth:
>
> We experienced great caching issues which would not all be solved
> using the approach described below. Remember that cache involves
> multiple versions and schemes of browsers, proxy servers, firewalls,
> network routers and servers.
>
> In my experience, the only way to "beat them all" in one action is to
> ensure that every URL is unique.
>
> For dynamically-generated pages, we append what we call a "no-cache"
> argument to every URL. At NCOL, we have standardized on a hash of the
> currenttimestamp, like so:
>
> &_nc=<@CIPHER action=hash str=<@CURRENTTIME>>
>
> For statically-generated pages, we add a large random number,
> generated in JavaScript, to ensure that every browser display (even
> those presented by the browser back button) has a unique URL. There
> are several ways to do this. We usually use:
>
> <script language="javascript">document.write('<a href="whatever.taf?'
> + Math.round(Math.random()*1000000000) + '">Your Link
> Here</a>')</script>
________________________________________________________________________
TO UNSUBSCRIBE: send a plain text/US ASCII email to [EMAIL PROTECTED]
with unsubscribe witango-talk in the message body
