On Nov 6, 6:48 pm, AndyWins <[email protected]> wrote: > > http://code.google.com/p/gmaps-api-issues/issues/detail?id=1902
Someone beat you to it: http://code.google.com/p/gmaps-api-issues/issues/detail?id=1895 I don't think anyone has actually demonstrated why the callback parameter is necessary. As far as I can see it shouldn't be needed server-side because there are other means of getting the data and processing it (eg XML); and client-side the normal GClientGeocoder of the API is expected to be used. So Google has tightened up the security and using an *undocumented* parameter now fails. Using the HTTP call in a documented fashion doesn't. Unless I've missed something, nobody has demonstrated why the callback is necessary and should be documented. I think that this is needed if the reported Issue(s) are not going to be marked as "WontFix". Andrew -- You received this message because you are subscribed to the Google Groups "Google Maps API" 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-api?hl=en.
