Looks good. And thanks for the confirmation (from your website):
// IE fires a loaded-event even in case of a failure (error 500),
so if myData is not defined an error must have been occured
// print error message or whatever you want to do here
As I said, the event comes anyway, regardless of what error happened or
whether there is an error or not. That's what I wanted to make clear
with my latest posts, but I couldn't make it clear enough, I guess. So
basically the "onreadystatechange" event is helpful in combination with
the check of an internal flag (or so) only, as you do, otherwise it
tells nothing useful. But also in this case it doesn't help you, if the
reply arrives late.
BTW: For FF the "onload" event fires too (similar to IE "loaded), so
that leads us to a funny "Success" and "Error - timeout" combination on
the same page (Version C, case 2a and 2b). I think, this is what William
pointed out with "late, but arriving response". In contrary to IE, the
"onfailure" fires on 500 (and would probably throw for 404 too, I hope),
thats good.
So the timer approach is OK, but seems to have the potential to make the
things worse with contradictory statements (see above). I have opted for
plain JSONP, without timers, without events. This let's the viewer alone
with missing parts of the map, in case of error, but that's a matter of
habit for the whole web.
Regards
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
