|
»
« Return to Thread: Passing named parameter without the URL
Re: Passing named parameter without the URL
by Derrell Lipman
::
Rate this Message:
On Mon, Nov 17, 2008 at 3:50 PM, Jean-Baptiste BRIAUD -- Novlog <j-b.briaud@...> wrote:
If you have form fields, then a different transport will be used. Without them, you were getting the XmlHttp transport. That transport, however, doesn't support form fields, so you're now getting the IFrame transport. Yes, what you see on the server will be slightly different. You'll see form fields since you're saying setFormField(). :-) You can expect, however, that as long as you don't change the parameters of your request (the parameters being synchronous vs async, selection or deselection of crossDomain, use or non-use of form fields, and your specified response type) that you'll continue to get the same automatically selected transport for every request.
Derrell
On 17 Nov 2008, at 21:45, Jean-Baptiste BRIAUD -- Novlog wrote:On 17 Nov 2008, at 21:21, Derrell Lipman wrote:That may explain something :-)On Mon, Nov 17, 2008 at 2:25 PM, Jean-Baptiste BRIAUD -- Novlog <j-b.briaud@...> wrote:
Hi,
I'm using io.remote.Request and I'm trying to pass named parameters
with setParameter method.
http://demo.qooxdoo.org/current/apiviewer/#qx.io.remote.Request
Unfortunatly, I found my param name and value always encoded in the
URL : &name=value
How can I pass the parameter inside the HTTP request without the URL ?
Using setParameter() specifically tells it to encode the parameters in the URL. I believe you're looking for setFormField().
Strangely, when I use setFormField, the request is not submited ...OK, I managed to make it work with setFormField but from my backend point of view, it look like using form and setting a request parameter is not exactly the same.Could one confirm that using form and using request parameter is different or is the same ?
If you have form fields, then a different transport will be used. Without them, you were getting the XmlHttp transport. That transport, however, doesn't support form fields, so you're now getting the IFrame transport. Yes, what you see on the server will be slightly different. You'll see form fields since you're saying setFormField(). :-) You can expect, however, that as long as you don't change the parameters of your request (the parameters being synchronous vs async, selection or deselection of crossDomain, use or non-use of form fields, and your specified response type) that you'll continue to get the same automatically selected transport for every request.
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@...
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
« Return to Thread: Passing named parameter without the URL
| Free embeddable forum powered by Nabble | Forum Help |
