I suggest writing a server to fetch, geocode and cache the results. When your Javascript needs the data, instead of asking a simple proxy server to fetch it from the remote location, it asks your cacheing server for the data.
Because the geocoding is slow, your cacheing server replies immediately with the data that it currently has in its cache, and then reads the external RSS feed to see if the feed has changed from the cached version. If the feed has changed, then your server sets about geocoding the entries. When that's finished, it stores the data plus geocode results in its cache. -- Mike Williams Gentleman of Leisure -- You received this message because you are subscribed to the Google Groups "Google Maps JavaScript API v3" 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-js-api-v3?hl=.
