Andreas Junghans <[EMAIL PROTECTED]> writes: > So it seems we need a switch that only adds the nocache parameter for > GET requests (although I'm a bit surprised that Rails doesn't allow > URL parameters in POST requests).
There are probably lots of different backend environments that will have various requirements, and we won't be able to meet all of them. This one, however, I suppose we can pretty easily meet. I've now checked in a change that PARAMETERS are not sent if using POST. I have left the FORM FIELDS properties intact, though. I think it's a lot clearer to always be able to say, "Parameters are sent in the URL, Form Fields are sent as part of the form. Hugh Gibson <[EMAIL PROTECTED]> writes: > Also, I don't understand why you have to switch to IFrame... Because that is the only transport for which we build the form on which the parameters are sent, and thus have appropriate control to be able to add form fields. (However, I'm perfectly willing to be proven wrong. Patches to XmlHttpTransport that would send user-provided form fields will be gladly reviewed!) Derrell ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
