On Sat, Feb 27, 2010 at 13:06, Jörg Sawatzki <[email protected]> wrote:
> var r = new qx.io.remote.Request("/fs/mkdir.json/"+path, "POST",
> "application/json")
> r.setFormField("name", name);
>
I see what's happening. You're calling setFormField which forces the use of
IFrame transport instead of the much more well-tested (and more appropriate
for most applications) XmlHttp transport. You've hit upon the following
code:
/**
* Returns the current status code of the request if available or -1 if
not.
* This method needs implementation (returns always 200).
*
* @return {Integer} status code
*/
getStatusCode : function() {
return 200;
},
The issue that form fields implicitly cause use of IFrame transport is a
known issue, although it hasn't come up in a long time and I didn't notice
that call initially. Since you likely don't actually require the IFrame
transport, instead of calling setFormFields, add the field as a parameter
with request.setParameter(name, "name", true); Note the third parameter,
which indicates that it should be added to the data, not to the URL as would
be done with a GET request.
This should solve your problem if you don't actually need to be using the
IFrame transport.
Cheers,
Derrell
------------------------------------------------------------------------------
Download Intel® Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
