Lawrence, In Witango 5 variabletimeout is no longer valid in Application or Domain scopes. Variables in these scopes are now persistent and do not timeout. T2K used to keep them for 3 days before purging them automatically.
If you do want to clear these scopes you can use the <@PURGE SCOPE="domain"> tag. If you want to do this regularly you can create a taf and call it via the crontab file. In the witangoevents.log file are you getting a similar line to this: [ 937] 2003-05-30 10:46:09 RUNTIME INFO Skipped empty startup URL Phil On 30/5/03 8:30 AM, "Lawrence Reeve" <[EMAIL PROTECTED]> wrote: > I am in the process of converting from Tango2k on MacOS 9 and WebStar > to Witango5 and Webstar on OS X 10.2. I have run into a couple of > problems. > > You can no longer assign a variabletimeout in domain scope, as > witango generates an error (although the documentation gives an > example in domain scope). I used to set this to 0 to keep domain > variables alive all the time. What is the strategy for getting this > functionality under the new version. I want to keep the system > variable set to 30. > > Also, I have had no luck getting the startupurl to work. Webstar used > to show 'sent startup url' but no such entry appears in the webstar > log now. > > Any ideas? ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/maillist.taf
