Same here. The problem disappears!
Thanks!
Mvg,
Ralf ( @ gong.nl // 06-49147635 )
On Fri, Jul 3, 2009 at 12:08 PM, Ian Horst wrote:
> I confirm - disabling "show XMLHttpRequests" in firebug console solves
> the problem. I'm still able to see requests in net tab.
>
> Thanks,
> Ian
>
> 2009/7/3
I confirm - disabling "show XMLHttpRequests" in firebug console solves
the problem. I'm still able to see requests in net tab.
Thanks,
Ian
2009/7/3 Andreas Junghans :
> Hi there,
>
> Am 02.07.2009 um 21:29 schrieb Ralf Nieuwenhuijsen:
>
>> I've hit this one as well. Anecdotal confirmation here. T
Hi there,
Am 02.07.2009 um 21:29 schrieb Ralf Nieuwenhuijsen:
> I've hit this one as well. Anecdotal confirmation here. The
> qx.io.remote.RequestQueue.getInstance() has .__queue as empty at
> that point.
> Which is likely the reason it does not start the new request.
> Perhaps this has to
I've hit this one as well. Anecdotal confirmation here. The
qx.io.remote.RequestQueue.getInstance() has .__queue as empty at that point.
Which is likely the reason it does not start the new request. Perhaps this
has to do with the new security changed with remote-io in FF3.5?
Mvg,
Ralf ( @ gong.nl
Hi Ian,
thanks for reporting this. Could you please file a bug report for this?
thanks,
Alex
On Thursday 02 July 2009 Ian Horst wrote:
> Hi all,
>
> RequestQueue handles the first 3 requests fine in FF3.5, but the
> following requests in queue time out ALWAYS.
>
> Code to replicate.
>
Hi all,
RequestQueue handles the first 3 requests fine in FF3.5, but the
following requests in queue time out ALWAYS.
Code to replicate.
qx.core.Setting.set('qx.ioRemoteDebug', true);
for (var i = 0; i < 4; i++) {
var request = new qx.io.remote
