The goecoder object itself is using JSONP with cross domain capability already. If you are talking about sending to Google's geocoding service directly without through the API, then it's a Term of use issue, and it appears the server did some checking on the callback method name and will reject if the call is not from the API.
On Nov 11, 12:26 am, Alan94539 <[email protected]> wrote: > Is there a way to submit reverse geocoding requests via JSONP? Or is > there a more convenient (better?) way to get around same-origin-policy > security? --~--~---------~--~----~------------~-------~--~----~ 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 [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-js-api-v3?hl=en -~----------~----~----~----~------~----~------~--~---
