======================================================================== http://mondrian.corp.google.com/file/8305270///depot/googleclient/gears/opensource/gears/geolocation/gps_location_provider_wince.cc?a=2 File //depot/googleclient/gears/opensource/gears/geolocation/gps_location_provider_wince.cc (snapshot 2) ------------------------------------ Line 361: MakeReverseGeocodeRequest(position_); I fear for the following scenario: if you are moving relatively fast, you will likely get a quite a few calls to HandlePositionUpdate() in a short interval. If the JS app is interested in addresses, as well, then it could be that it will miss out on a lot of position updates because the reverse geocoding requests take a lot longer to complete and the listeners are updated only when the reverse geocoding completes.
I guess the discussion is again around the meaning of "gearsRequestAddress": if we treat it as a hint to the implementation to try and return an address whenever possible, then the listeners should be updated every time we have a significantly different position, irrespective of the state of the currently running reverse geocoding request. If we treat it as a mandatory requirement, then the current behavior is correct. Personally, I'd prefer the first option. Which one do you prefer? ------------------------------------ Line 412: whitespace ======================================================================== -- To respond, reply to this email or visit http://mondrian.corp.google.com/8305270
