On Mon, Sep 22, 2008 at 2:11 PM, Jean-Baptiste BRIAUD - Novlog <
[EMAIL PROTECTED]> wrote:
>
> I would like to try qx.io.remote.Request for some AJAX request but in
> the doc it is stated that for 0.8 it need to be upgraded.
> Unfortunatly I'm not able to hack the example for 0.7...
0.8 qx.io.remote is working the same as 0.7, to the best of my knowledge.
>
>
> var req = new qx.io.remote.Request("http://localhost:8888/blabla";,
> "POST", "text/x-json");
One of the nice automated features with qooxdoo's remote request classes is
that it determines the most appropriate "transport" to use depending on the
needs that you've specified. There are currently three transports: XmlHttp,
Iframe, and Script. Each has unique characteristics that make it useful for
a particular job, but each also has limitations that make it unusable for
some jobs.
XmlHttp transport has these characteristics:
handles :
{
synchronous : true,
asynchronous : true,
crossDomain : false,
fileUpload : false,
programaticFormFields : false,
responseTypes : [ "text/plain", "text/javascript",
"application/json", "application/xml", "text/html" ]
},
Iframe transport has these characteristics:
handles :
{
synchronous : false,
asynchronous : true,
crossDomain : false,
fileUpload : true,
programaticFormFields : true,
responseTypes : [ "text/plain", "text/javascript",
"application/json", "application/xml", "text/html" ]
},
and Script transport has these characteristcs:
handles :
{
synchronous : false,
asynchronous : true,
crossDomain : true,
fileUpload : false,
programaticFormFields : false,
responseTypes : [ "text/plain", "text/javascript",
"application/json" ]
},
You'll note that if you tell your Request object that you require a
synchronous request, only XmlHttp transport could be used because the other
two don't support synchronous requests. Similarly, if you specified that
your request required cross-domain, it would have to use the Script
transport since that's the only one that handles that need.
In your case, you are specifying that the response type is text/x-json, but
that response type is not handled by any of the three transports. I would
guess that that's why it's telling you that no transport implementation is
available to handle this request.
Hope that helps.
Derrell
-------------------------------------------------------------------------
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
