I think I solved it. The culpret for me was firebug. I disabled that guy and it works fine. This sucks though cause I truley <3 firebug. But I think what happened was firebug was delaying/freezing communication between my internal server and google's library.
Hope that helps someone Alex On Mar 10, 12:49 pm, Rossko <ros...@culzean.clara.co.uk> wrote: > The poster seems to running at least seven internal servers, which > might be connected to the problem. Most developments would involve > just one or maybe two. But as you say, we've no idea what their > hitrate is or if they are overusing services like geocoding. Maybe > Google haven't changed anything at all, but 'approaching release' just > means increased activity that's crossed a threshold. Google won't > tell us exactly, that's for sure! > > It does seems a bit daft to be 'approaching release' without giving > Google some indication of intent .... --~--~---------~--~----~------------~-------~--~----~ 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 google-maps-api+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/Google-Maps-API?hl=en -~----------~----~----~----~------~----~------~--~---
