OK, I'll do some digging on the CrossDomain request stuff.
Thanks,
-Eric
From: Derrell Lipman [mailto:[email protected]]
Sent: Tuesday, July 31, 2012 2:35 PM
To: qooxdoo Development
Subject: Re: [qooxdoo-devel] qooxdoo RPC
On Tue, Jul 31, 2012 at 2:29 PM, Eric Paul <[email protected]>
wrote:
Thanks for your prompt reply.
I do not need a synchronous call but I do need to crossDomain support.
Whenever I use the callAsync then nothing happens at all. No error-nothing.
That's why I was using "call".
A ".net service" is really just a page written in .net to handle the
JSON-RPC requests. The page I listed:
http://74.143.64.2:5040/Handler1.ashx
is a real page. If you visit it in web browser you can navigate to a test
interface to see how it works.
If I use any other tool to make a JSON-RPC request to that page they all
work. If I use fiddler and send:
{"data":"test"}
It returns my "success" message and
{"id":1,"method":"WriteFile","params":{ "data" : "test"}}
Ok. With a cross-domain request, which uses the Script transport, you can't
just return data. Take a look at the documentation, which hopefully makes it
clear, and in particular at the section labeled "Cross-Domain Requests":
http://demo.qooxdoo.org/current/apiviewer/#qx.io.remote
You can also search for JSONP which is the current standard that is very
similar to the qooxdoo implementation in the Script transport.
Cheers,
Derrell
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
