Hi, Am 29.01.2007 um 22:28 schrieb Hugh Gibson:
>> Ok, that makes perfect sense. That means I have to leave >> setParameter() always putting parameters in the URL even if POST, >> which means I'll need another property for adding form fields. >> That's >> reasonable, I think, and is more flexible. > > Not necessarily. POST should never be cached anyway, as it is for > updating values to the server. Yes, but you can also use the Request class for GET requests where the parameter might be necessary. > See http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html#sec9.5 > > "Responses to this method are not cacheable" > > So there's no need to add the parameter. In fact, as mentioned in > the bug report, it results in a malformed request. Quote from the bug report: "This bug is critical when using QooxDoo with Ruby on Rails because Rails framework does not allow to dispatch POST and PUT requests with any parameters within the requested URL." 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). Regards, Andreas ------------------------------------------------------------------------- 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
