exactly. it's funny, I never tried to get around the limitation before
but I had supposed it was possible basically because of the
possibility with the iframe workaround. I hadn't expected that it
would need to use the iframe hack to do it!


Cheers,
Bryan Rasmussen

On Wed, Nov 12, 2008 at 6:15 PM, Barry Hunter
<[EMAIL PROTECTED]> wrote:
>
> Not strictly true. Subdomains can talk to each other (or least they
> could, havent used this technique for a while now)
>
> http://fettig.net/weblog/2005/11/28/how-to-make-xmlhttprequest-connections-to-another-server-in-your-domain/
>
>
>
> On Wed, Nov 12, 2008 at 4:54 PM, yejun <[EMAIL PROTECTED]> wrote:
>>
>> XHR require the host name be exactly same. So you have to server your
>> page and xml both off same server.
>>
>> On Nov 12, 4:49 am, "bryan rasmussen" <[EMAIL PROTECTED]>
>> wrote:
>>> As per the subject:
>>>
>>> I have an ajax based application, I figured I could offload some of
>>> the static XML files I need to serve via XHR off to GAE, then when I
>>> am doing a new XHR request check for a file, if that file does not
>>> return 200 I am currently not accessing GAE so switch to some other
>>> service. Does this seem reasonable. Another problem is obviously that
>>> I will need to do some DNS settings to make sure that I can serve my
>>> initial request from my domain and then get further requests via  XHR
>>> from app engine. Has anyone tried a similar setup or have suggestions,
>>> note problems with the approach?
>>>
>>> Thanks,
>>> Bryan Rasmussen
>> >
>>
>
>
>
> --
> Barry
>
> - www.nearby.org.uk - www.geograph.org.uk -
>
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google App Engine" group.
To post to this group, send email to google-appengine@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/google-appengine?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to