Exactly. The "straight" JSON, delivered until now by my server, didn't
work the very first attempt. Reason: I was missing the assignment
statement, so the plain JSON object "{lat=xxx, lon=xxx}" had to be
delivered padded with a variable assignment, e.g. "data = {lat=xxx,
lon=xxx}" by the server.
But Micheal: Why this?
JSON is not executable JavaScript and cannot be used cross-domain without a
proxy.
I think, "cross-domaining" is of course possible, but it is probably
hard to deal with the results? The server side is called in any case...
Or do I catch that wrong? For me XMLHttpRequest is not cross domain and
cannot be used w/o proxy, that's for sure.
Regards
Regards
Michael Geary schrieb:
>> From: Lance Dyas
>>
>> JSON is javascript (and typically implemented as JSONP ..
>> with a call back) it is cross domain and involves attaching a
>> script tag to the header...which the browser downloads and
>> processes... it doesnt involve using xmlhttprequests its
>> what you saw in Jurgens post but you probably already figured
>> that out by now.
>>
>
> Just to be precise...
>
> JSON is not executable JavaScript and cannot be used cross-domain without a
> proxy.
>
> JSONP with a callback is executable JavaScript that can be used
> cross-domain.
>
> Details in my other post from this morning:
>
> http://groups.google.com/group/Google-Maps-API/msg/c5336d4e3286fb6b
>
> -Mike
>
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
