On May 10, 4:33 pm, mp- <[email protected]> wrote: > > What happens is that if I have to load the map first, it's a serial > blocker until the Google Map fully loads that I can then geocode and > query the database to find what push pins should be shown. > > In the case of using the geocode via HTTP, I can attempt to parallel- > ize this step more. > > So what I want to do (hopefully) is: > > I can geocode via HTTP (super quick b/c of now big api download) the > long/latitude. Temporary display a *static* google map to make the web > page appear to load fast. Then at the same time (parrallel) do both > querying my database (using the long/latitude info) to find the > relevant push-pin markers while loading the full blown interactive > Google Map.
So what you need to do is a two-stage data retrieval. Pass the user entry back to your server, geocode it there and get the server to construct the page with the static map <img> tag and (say) a hidden field with a unique reference in it. Then once the API is loaded do a GDownloadUrl to pass that unique reference to your server and get the relevant marker data. I think. 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 -~----------~----~----~----~------~----~------~--~---
