On Thu, Jul 23, 2009 at 9:10 AM, skar <[email protected]> wrote:
> Christian Schmidt wrote: > > I'm not a not a expert for qx.io.remote.Request as far as I know is it > > not possible to reuse one request instance. You have to use one request > > instance for each request. > > > > I have looked to the current implementation, the code does explicit set > > the content only if the request was successful. I don't why it is > > implemented this way, but I would say this is a bug. Could you please > > open a bug report for that? Thanks! > > > Thanks chris. Will open the bug report. But the problem isn't just the > reuse of the request. I load the qooxdoo app in a new firefox process > with new profile, and any request which has "403" and a content returned > has only the 403 shown as status, but the content is shown as null. > However, firebug and wireshark show the content too reaching firefox. > That's one problem. Another is when a successful request is followed by > an unsuccessful request, the second "failed" request has the content of > the previous "completed" request, showing neither null or the real > content returned from the server/rails. In this case too, firebug and > wireshark confirm correct return of content from rails, but only the 403 > status is shown correctly by qooxdoo. > There are two issues here. Firstly, you should not reuse the Request object. If you create a new request object, you wouldn't (couldn't) see the content of a previous request in your new request's response. Request objects are intended to be single-use. The other issue is that the content is not being recorded when the type is "failed". See my response in your other message on this topic, and try applying the patch I provided. Once you confirm the patch solves your problem (assuming you're using a unique Request object for each request) and you've created the bug report, I'll apply the fix and close the bug. Cheers, Derrell
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
