On Nov 24, 4:39 pm, Lara <[EMAIL PROTECTED]> wrote: > Hi everyone, > > Thanks for all the spirited discussion and suggestions. I am still > trying to digest all this, and get up to speed with JSON, proxies, etc > (and work on other projects). Unfortunately, my web host doesn't > support PHP on the server we use (Windows 2000 with IIS). > > In response to Bratliff, I will say that I hope to build connections > to WFS data that are dynamically updated, so that I don't have to pay > attention to when updates have been made, how often, etc., so that I > know that my users always have the most current data. > > Thanks again, when I figure something out, I will post a link to my > solution, but in the meantime, if anyone else has additional thoughts, > examples, I'd love to see them. > > cheers, > Lara
Since your server will have to interact directly with the WFS host to avoid cross-domain complaints, you might do the XML document parsing on your server & cache the results. If the XML document is too old (one day perhaps), fetch a fresh copy. Otherwise, use the cached copy. Your users will see less delay. Parsing in the browser is slow. Each user will have parse the same XML document instead of doing it once on your server. Google's GGeoXml is a good example to follow. The server does the bulk of the work. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
