Because the geocoder request is cross domain it must be loaded via JSON and callback, which means the API must be able to include a remote JS, into the page.
You could probably use the same technique to load the Maps API, by not using a script tag directly. Example: http://code.google.com/apis/ajax/documentation/#Dynamic I beleive v3 is available via the common loader. So you don't need to save the load JS locally, which is always going to end badly. 2010/1/26 Chris Apolzon <[email protected]>: > My current framework is unable to do remote js includes properly, so > I've resorted to a hardcoded "google.js" which consists of the initial > load code returned by the default remote inclusion line. Obviously > this freezes me to a specific release of the API, but my issue is with > the geocoder service. Whenever I use the hardcoded js API include, my > geocoder requests are denied stating: > Your client does not have permission to get URL <code>/maps/api/js/ > GeocodeService.Search?query=.... > > Is there any way for me to use a non-remote copy of the API and still > have access to the geocoder service? > > Thanks. > > -- > 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. > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - -- 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.
