2009/11/9 Mike Williams <[email protected]>: > Wasn't it Andrew Leach who wrote: > >>I don't think anyone has actually demonstrated why the callback >>parameter is necessary. > > My understanding is that GClientGeocoder uses it to match the replies to > the requests, thus allowing multiple geocode calls to be in flight at > the same time, using the same GClientGeocoder instance. The server sends > back the callback parameter, and GClientGeocoder uses it to determine > which .getLocations() or .getLatLng() call to call back.
My understanding of Andrews question is why a user is using it in *user code* - the API can use it behind the scenes. But its not a documented parameter and a user shouldnt be using it directly (for example with jquery) The Maps API provides two interfaces to the Geocoder, GClientGeocoder in a browser. And a HTTP interface for access from server side code. Nowhere is it documented that Google offers a direct query interface for using in a browser. And as such it doesnt fall within the terms of use. > > Compare GDirections, which doesn't use a callback parameter. If you make > two simultaneous requests with the same GDirections instance, you lose > one of them. > > -- > Mike Williams > http://econym.org.uk/gmap > > > -- > > 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. > > > -- Barry - www.nearby.org.uk - www.geograph.org.uk - -- 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.
