Thank you very much for your explanation. I am going to spend some time looking into all this and then report back.
On Aug 28, 2:04 am, Rossko <[EMAIL PROTECTED]> wrote: > > I am not sure what you are saying... > > Okies, I'm saying that geocoding takes a finite time, a relatively > long time in terms of server-side script execution. Your data has to > go off to Google and a reply come back. Exactly how long this takes > is unpredictable but the average will usually vary by time of day > because server workloads and internet traffic varies by time of day. > > We don't know how your server side script handles this delay. > Does it just wait forever? (probably not!) > Does it wait for a fixed time, i.e. a timeout period? Could be, if so > how does it handle a timed-out request .... your script might retry > the request. Or it might display an error message. Or it might send > empty data to your webpage... ? > Or your server script might handle it asynchrously, which is whole > topic in itself, but often trips people up. > > On top of that, there are various reasons why Google might reject your > request temporarily, and not send you the data, but send an error code > instead. Mike knows this will happen sooner or later, which is why > he's banging on about what your server script does if it gets a > response like that ... guessing that it blindly carries on as usual > and sends empty data to your webpage. > > cheers, Ross K --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
