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. 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.
