Hello List,
I'm attempting to migrate an in-house ajax transport layer over to the qx
0.8 transport layer.
My first experiment looks something like this:
__handleClick : function(e)
{
var app = qx.core.Init.getApplication();
// Create HTTPRequest
var req = new qx.io.remote.Request("
http://myhostname/mediawiki/index.php/";, "GET", "text/plain");
req.addListener("sending", app.__onsending, app);
req.addListener("receiving", app.__onreceiving, app);
req.addListener("completed", app.__oncompleted, app);
req.addListener("aborted", app.__onaborted, app);
req.addListener("timeout", app.__ontimeout, app);
req.addListener("failed", app.__onfailed, app);
//req.setUsername(null);
//req.setPassword(null);
req.setTimeout(10000); // milliseconds
req.setCrossDomain(true);
req.send();
},
This "works" in as much as the response from my local mediawiki server is
returned, but I am confused by the triggers my listeners are getting. I
would have expected to see the sending, received and completed listeners
being triggered (in that order) when the request is successful. However,
instead I am seeing only the timeout listener triggered -- even after the
response has been successfully returned. I observe the same behaviour is FF
and IE.
Does anyone have any insight they can share?
Thanks,
Simon
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
