> You server should not return the JS file unless it has complete > results. Do whatever you have to do then return the JS file. > > Also, if you will be recalling the same file using the same name, you > will have to defeat your browser's cache with a bogus parameter in the > URL. > > ?? So, what I have is a web site, rendered using ASPX. The site presents a form for parameters used in a server side query and the div for the map. The query is driven by '<script id="xx" src="myserverside.aspx"></script>' in the head. Onclick the form is posted to the server, the server returns JSONP in a uninterrupted execution chain. (Query in, result out). But - if onreadystatechange="completed" for the script object, the JSONP object is not yet present.
Hence I'm using the timer approach. In body onload() I'm starting a timer (as Jürgen describes) and wait for the appearance of the JSONP object. If it is present, the map is rendered with the markers, which coordinates are provided by the database query. This works. Until now my page did GDownloadUrl and rendered the complete map in the async callback after completion. With the known restrictions for IE6 and ActiveX. The bogus parameter was the date(). Right now my approach is missing that bogus parameter, but can be implemented, using "on demand JS" instead of static script placement in the html markup... Alternatively the server could render the complete page including all the required JS. Will see, whether I should better use this approach. > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
