Wasn't it Andrew Leach who wrote: >and you can only use one geocoder object for a single request (re-using >it while it's waiting for a response will wipe out the current query).
That's not true of GClientGeocoder(). It is true of GDirections() and GLocalSearch(), but GClientGeocoder() is smarter than them. GClientGeocoder adds a unique identifying parameter to each request that it sends to the server. The server simply that parameter as part of the reply. The client code reads the returned parameter and matches the reply to the entry in its list of pending callbacks that has the same identifier. -- 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.
