Hi Derrell,
Thanks a lot, that's very kind !
Once again, I'd like to hightlight another good point of qooxdoo : the
community.
Now, about the patch itself, could you confirm it patch the
io.remote.Request class ?
I never have to deal with qooxdoo patch, but what should I do then ?
I'm afraid I need to be educated on that point. This is not lost since
I'll be able to help on testing other patches after that :-)
I think the simplest thing will be to :
* checkout the HEAD from SVN,
* use the qooxdoo build to produce that qooxdoo in one file with Petr
json config file
* test against my code.
I have a big company meeting now, but I'll check all that tomorow.
JBB.
On 19 Nov 2008, at 16:02, Derrell Lipman wrote:
On Tue, Nov 18, 2008 at 8:31 AM, Jean-Baptiste BRIAUD -- Novlog <[EMAIL PROTECTED]
> wrote:
On 18 Nov 2008, at 14:23, Derrell Lipman wrote:
On Tue, Nov 18, 2008 at 8:14 AM, thron7
<[EMAIL PROTECTED]> wrote:
>> Using setParameter() specifically tells it to encode the
parameters in the
>> URL. I believe you're looking for setFormField().
>>
> If you have form fields, then a different transport will be used.
This is true, but I strongly object against the XmlHttp transport
being
restricted to GET and URL parameters. If this is really the case,
somebody has to open up a bug for it. XmlHttp transport has to
support
POST and setParameters() working on the request body!
XmlHttp transport _does_ support POST. That's not the issue. The
issue which has been discussed in depth in the past is that even
with POST, it must be possible to add parameters to the URL. You
(and the reset of those in this discussion) are right that there
*should* be a way to add parameters to the POST request body.
There's just no way to explicitly specify that currently. This is
just one of many issues that have been addressed in the past, that
should be addressed in a rewrite of qx.io.remote.*
I didn't know it was discussed before, sorry ...
So, I do agree with you : parameter to the POST request body is a
need.
Jean-Baptiste, would you please test the attached patch (or pull
from SVN; I've checked it in). Note the new parameter available to
setParameter() which specifies whether you want the parameter to be
in the URL or as data. This should do exactly what you're looking
for. Let me know whether this works properly for you.
Cheers,
Derrell
<
y
.patch
>
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
