On Tue, 03 Jul 2001 22:15:26 -0500, I wrote:
> [EMAIL PROTECTED] wrote:
>> - is there an elegant way to prevent Arachne from reloading a
>> dgi file?
> I'll have to think about that. <G>
Well, I've given it a bit of thought and experiment.
I'm not sure you would call any of these elegant, but they work -
at least under some circumstances.
The easiest way that I can see to prevent Arachne from re-running a
.DGI is to manipulate the history.lst.
This can be done in several ways:
If the .DGI doesn't have an [nnn] entry, then you can remove all trace
of your .dgi call from history.lst thusly:
|TYPE history.lst |FIND /V /I "my.dgi" >history.lst\n.....
Or you can force some special page to become the "back" target:
|ECHO file:PPP_INIT.htm >>history.lst\n....
Or you can terminate with prejudice:
|DEL history.lst\n.....
Or, if the .DGI is of the [nnn] variety (that won't permit "\n" commands)
you can sneak up on it by calling a .ASF instead of a .DGI.
ASFs currently kill the history.lst - I don't know if that is by design.
Maybe there is even a way to copy the history.lst to itself minus the
last entry. I'll leave further experiments up to you because I don't
know which will fit your situation best.
It would be nice if there was a <NOHISTORY> tag or mime.cfg operator.
- Clarence Verge
- Back to using Arachne V1.62 ....
