My apologies on this one. Shortly after posting, I realized that it was simply a proxy issue and now have it using ye olde openLayers proxy script and... voila! Much happiness. JSON would be preferable, but thus far geoserver doesn't support jsonp, and json isn't supported at all for wms queries. My thanks for the answer, nonetheless.
-Josh On Fri, Sep 5, 2008 at 11:48 AM, warden [Andrew Leach - Maps API Guru] < [EMAIL PROTECTED]> wrote: > > On Sep 5, 4:41 pm, "Josh Rosenthal" <[EMAIL PROTECTED]> wrote: > > > > Has anyone dealt with/implemented similar? > > The issue has come up many many times. The answer is either a proxy > script on your own server (which can serve data it collects from > elsewhere); or to use JSON instead of KML as that doesn't suffer from > the same cross-domain restrictions. > > Searching on "proxy script" or "JSON cross-domain" or something > similar should return some substantive threads. > > 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 -~----------~----~----~----~------~----~------~--~---
