Wasn't it Mike Williams who wrote: > >Without a link to your page, we can only guess at what's happening. > >One possibility is that the GGeoXml server is caching the old data, and >that you're using the same URL for the new data. To avoid the data being >cached, you need to use a different URL when the data changes. It would >be a good idea to do that anyway, in case you ever have two users >accessing your site at the same time but wanting different data.
Yes. That's exactly what you're doing. Notice that Javascript variables are case specific, so this code var miUrl="http://www.ozeanus.com:9069/GeosII/rutas.kml"; var miURL=miUrl+"?nocache="+(new Date()).getTime().toString(); creates miUrl: http://www.ozeanus.com:9069/GeosII/rutas.kml miURL: http://www.ozeanus.com:9069/GeosII/rutas.kml?nocache=1240041046988 But then you use the wrong one on this line: geoXml = new GGeoXml(miUrl); Note, however, that this will all go wrong if two people use your page at the same time. They could easily end up with each other's data. Your overall strategy for obtaining the data needs a significant redesign. -- http://econym.org.uk/gmap The Blackpool Community Church Javascript Team --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
