In order to eliminate an API change as the culprit in an issue like this, it's quite a simple matter to specify a back-level API version in your key string. That is really the obvious first step if you're so adamant that it's an API issue.
On Oct 29, 2:24 pm, Rossko <[EMAIL PROTECTED]> wrote: > > Ok, thanks a lot Andrew ... so, it is simply a coincidence that it > > stopped working fine since the api version upgrade. > > I'll move my investigations on the server-side, then. > > The API changes virtually every week, so there always be some recent > changes. > Maybe you're hitting a maximum line count output, or more likely a > timeout condition, as the output doesn't seem to be consistent. > > When the Roma searches were working for me in terms of getting > complete pages, they were still timing out in the browser with > 'javascript taking too long' type errors. You're going to need some > means of limiting the amount of markers here, no customer really wants > a map with 800 possible B&B to choose from on it. > > 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 Google-Maps-API@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
