UPDATE:
I have just been reading the post by Johnster (an the suggested links by geozip), whilst I appreciate WHY this limit is in place, and the suggestion that you should primarily use Client requests, and fall back to server requests if these fail). With this limit, and cloud computing (which Google themselves are obviously a serious provider - esp. for us!) - this would appear to equate to - the 'strategy' of fall back to server will NEVER be an option. Our App, for many reasons, does not want to 'trust' the reverse geocoding received from the client, so therefore we have not option but to request this from the server. Reading the docs, I am not sure that even moving to Premier at this point would actually solve the problem (it's not clear from the docs!). The right answer would appear to be to go to the KEY method that was previously used, and is still being promoted by 'other' google tools - Search, Translate, etc. It may be me, but it would appear that the Maps V3 API is moving away from the 'Google Way'? Surely, this can only be a BAD thing, and will prevent the use of this functionality within cloud environments. Please help (ASAP ;-) ) Dave -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" group. To post to this group, send email to google-maps-js-api...@googlegroups.com. To unsubscribe from this group, send email to google-maps-js-api-v3+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-maps-js-api-v3?hl=en.
