Javascript, webservices and Firefox

[Nightcrawler]

I recently moved over a bunch of functionality to use javascript and
webservices. I ran into the issue where a webservice taking longer
than 10 seconds to respond will cause Firefox to throw a fit and show
the "script has stopped responding" warning.

Is there a way around this? What can possible be done so that firefox
keeps the connection alive without showing that annoying message.

All I can find about this online is to change the firefox settings in
about:config but this is not a solution to me. That would require
every firefox visitor to change their settings to view my site.

Any input would be appreciated.

Thanks

[Randy Webb]

Nightcrawler said the following on 12/12/2007 2:27 PM:

I recently moved over a bunch of functionality to use javascript and
webservices. I ran into the issue where a webservice taking longer
than 10 seconds to respond will cause Firefox to throw a fit and show
the "script has stopped responding" warning.

Is there a way around this? What can possible be done so that firefox
keeps the connection alive without showing that annoying message.

All I can find about this online is to change the firefox settings in
about:config but this is not a solution to me. That would require
every firefox visitor to change their settings to view my site.

Any input would be appreciated.

Find a faster webservice.

--
Randy
Chance Favors The Prepared Mind
comp.lang.javas cript FAQ - http://jibbering.com/faq/index.html
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/

[Nightcrawler]

That's the only solution?

[Richard Cornford]

Nightcrawler wrote:

I recently moved over a bunch of functionality to use
javascript and webservices. I ran into the issue where
a webservice taking longer than 10 seconds to respond
will cause Firefox to throw a fit and show the "script
has stopped responding" warning.

Is there a way around this?

<snip>

You have posted no code so nobody knows what you are actually doing. So
the best you will get are guesses. Two possible explanations for your
symptoms stand out to me.

1. You are actively polling the - readystate - of the
response in a - while - (or similar) loop.
2. You are making synchronous requests where you should
be making asynchronous requests (as only asynchronous
requests should be used, regardless of the additional
complexity that requires in handling multiple
asynchronous inputs).

The latter seems more likely (as the former is insane) and so you solve
the problem by only making asynchronous requests.

Richard.