Your idea was correct. Requiring the browser to get the latest version of a page every time seemed to work. Thanks for the tip.
Peter - > Make sure you browser isn't caching anything. Set it to check for new > content each time. Robert > > -----Original Message----- > From: Peter Fogg [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 06, 2005 4:55 PM > To: [email protected] > Subject: RE: Witango-Talk: Strange behavior in application scope > > NOt that I know of. The server is on my local workstation and is not > serving pages to anyone but me. > > Peter - > > >> Is the server under any load (or answering other requests at all) during >> your testing? >> >> -----Original Message----- >> From: Peter Fogg [mailto:[EMAIL PROTECTED] >> Sent: Wednesday, April 06, 2005 12:21 PM >> To: [email protected] >> Subject: Witango-Talk: Strange behavior in application scope >> >> The environment: >> Witango Dev Studio 5.5.08 >> Witango Server 5.5 on a Windows 2000 Server 5.0.2195 with SP4 >> a TCF, COMMON >> a TAF, INDEX., which instantiates Common in application scope >> a TAF, EXISTENCE, which tests for the existence of Common in >> application scope >> a TAF, PURGE, which purges Common from application scope. >> >> The strange behavior: >> run INDEX which instantiates COMMON in application scope >> run EXISTENCE which confirms that COMMON is in application scope >> run PURGE which says that the opbect COMMON has been purged from >> application scope >> run EXISTENCE which states that the object COMMON still exists in >> application scope >> refresh EXISTENCE which now states that COMMON is no longer in >> application scope >> >> if I now run INDEX, I receive this message: >> >> Error >> An error occurred while processing your request: >> File: home.taf >> Position: CreateCommonObject >> Class: Internal >> Main Error Number: -815 >> >> Cannot locate object. >> Common >> >> File: home.taf >> Position: CreateCommonObject >> Class: Internal >> Main Error Number: -622 >> >> The specified object instance could not be created. >> Common >> >> >> If I then refresh INDEX, it instantiates COMMON. >> >> Is there a delay when something is purged from application scope? Why >> does >> refreshing EXISTENCE after a PURGE change its mind? >> >> Thanks for any illumination provided. >> >> Peter - >> >> >> >> ________________________________________________________________________ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> >> ________________________________________________________________________ >> TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf >> > > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > > ________________________________________________________________________ > TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf > ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
