> 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).
Version B that is ;-) > In contrary to IE, the > "onfailure" fires on 500 (and would probably throw for 404 too, I hope), > thats good. Well, Chrome doesn't!! It fires onload (Success). Another point that makes me not feeling good about browser compatibility. Anyway, there not much to do wrong. Worst case is that the viewer gets a late error message (when the timer goes to action). >From above: >>Returning a JS file immediately without waiting for your server to >>produce results is not the way most people use JSON with a callback. >>The JS file should contain the results of the query. Otherwise, what >>purpose does it serve ? > >??!?! Who is returning what JS file while not waiting for results Hello!?!?! >Anybody home???!? :) I think what bratliff meant with JS file is the content of the script- tag that you are trying to load. The JSON object with the callback function wrapped around is. Nothing else. Of course the servers has to produce the response somehow and sent it back to your browser. That implies that you have to wait for the server to be done, otherwise there won't be an answer. Probably just a misunderstanding ;-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
