Chrome is multithreaded. Firefox and most other browsers are single threaded.
In a single threaded browser, the browser can't do anything else while your sleep() loop is processing, but Chrome can do other things, perhaps receive GDirections replies. Even when it works, it's not very polite to use 100% of your user's CPU power in order to do nothing. It's better to use setTimeout() or setInterval() which don't hog the CPU while they wait. -- Mike Williams http://econym.org.uk/gmap -- You received this message because you are subscribed to the Google Groups "Google Maps API" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-maps-api?hl=en.
