Well, what do you know?
I was developing this setTimeout() business -- I had four applets on the
page with just one 100-ms timeout running. Now we still may find that
there are problems with some browsers/platforms, but here's my observation:
1) Over the past few days as I've developed those getProperty() pages
I've had some pretty dramatic crashes of Mozilla/PC.
2) When I put four applets on the page and started polling them every
100 ms, all hell broke out. Talk about bizzare messages -- one was that
a function on the page suddenly "was not found" -- several times the
page dramatically froze or Mozilla just shut down completely or went
into its "you can't find me, nah-hah!" mode that requires
CTRL-ALT-DELETE processes killing. [Sort of reminded me of the day I (I
kid you not) watched as the applet I was trying to control stopped
responding -- and then I realized that the applet ON ANOTHER PAGE was
now taking my script commands. Ouch!]
3) Thinking this was almost surely a thread - thread collision problem,
I added the "synchronized" attribute to all the functions in my new
StatusManager and PropertyManager, and for good measure I also added it
to the main applet/browser interface methods getProperty() and script().
4) Could it be? Instant success! Sure looks like it. Do you suppose the
primary "unreliability" of callbacks stems from thread synchronization
problems? Maybe we should think about how other "gateway" methods
perhaps should be synchronized.
Bob
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
Jmol-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jmol-developers
