Web App issues with NetZero

Dan Soneson sonesond1 at southernct.edu
Thu Feb 26 11:29:47 EST 2004


I am experiencing something rather unexpected in a  web app that I am 
developing for my students. I have given them a splash screen 
application with just the engine, a button with a backscript, and a 
button that calls a stack down from the web. We’ll call this stack 
stack 1. The subsequent stack (stack 2) is simply a login screen, with 
fields for the student’s name and a button that downloads and opens 
another stack (stack 3) from the web. This third stack also has a set 
of links that download and open further independent stacks (stacks 4, 
5, 6…) as well.

This arrangement has been working fine for my students until one of my 
students switched her ISP from AOL to NetZero. When she now uses my 
splashscreen app, the button that accesses the login screen (stack 2) 
from the web seems to open a stack that has been cached somewhere. The 
button on stack 2 apparently can’t find stack 3, so when we click this 
button the application shuts down.

It is apparent that the stack 2 which her machine accesses is cached 
somewhere, because when I add a button to stack 2 and save it on the 
web, the old stack 2 is still called up on her machine. The problem 
seems to be connected with NetZero, since when we run her machine 
through an ethernet connection on our network, everything works just 
fine. But when we go through the modem by way of NetZero, the old stack 
2 appears and apparently cannot find stack 3 (standard “go URL “ 
command) so the program shuts down.

Has anyone had experience with this problem and if so, do you know of a 
workaround? Her machine is a Dell Inspiron laptop running Windows XP. I 
develop on a Macintosh, but none of the other students seem to have 
this problem, although they are all running various versions of 
Windows. I have fiddled around with the Internet control panel on her 
machine, clearing the cache and the stored list of websites visited, 
but still the problem persists.

TIA
Dan



More information about the use-livecode mailing list