Reload
Caveat
ConferWeb
Two pieces of
background information
- When you
submit your form for the conference thread or create a new thread, the
submission is handled by a program which (1) updates the appropriate file(s),
and (2) redirects your browser to the appropriate page so you can see
what you've done.
- In the normal
course of browsing, if you access a link which you've used before, the
browser (1) checks to see if the HTML or graphic is cached on the local
hard disk, and if it is (2) should ask the HTTP server whether the HTML
file's contents have changed since the cache was created. If it finds
that the cached HTML is current, it simply displays it, without downloading
the information again. The HTTP server presumably looks at the file-system's
"last modification" date or some such to decide if the file's changed.
Netscape has a
preference which controls the conditions under which it checks up on the cached
file. It is called "Check Documents" and is located in the "Cache and Network"
portion of the Preferences ("Options" menu).
For BEST RESULTS,
set this option to ALWAYS.
If you don't
do this, your browser may simply reload the unmodified local copy
of the edited page, giving you the impression that your update didn't work.
If all else
fails?
Simply TELL
YOUR BROWSER TO RELOAD the page. In Netscape that's command-R, or click
on the RELOAD button if it's visible. This forces the current page contents
to be retransmitted by the server, and everything will be OK. If that doesn't
seem to be working, try holding down the OPTION key when you click on RELOAD.
|
