> However, there's a restriction in Firefox that could be the cause
> of your problem. By default, Firefox opens only 2 connections to
> the same host at the same time (at least when using persistent
> HTTP 1.1 connections). It's easy to bump against this limit. In
> your case, you already
Hi Mike,
Am 11.01.2008 um 14:02 schrieb mg2:
> Is the mechanism in general (execute and get reply for Rpc Requests
> while
> one other Rpc Request is already waiting for reply) known to work
> in FireFox
> or is it probably a mistake in my code ?
It is known to work. I just tested it, and I
Hi Andreas,
Thank you for the reply.
HTTP pipelining was already disabled so this is not the cause of the problem
(also pipelining.maxrequest =4).
I also tried with mozilla (1.7.1) with the same result.
Is the mechanism in general (execute and get reply for Rpc Requests while
one other Rpc Req
Hi Mike,
Am 28.12.2007 um 02:21 schrieb mg2:
> If the 2.Rpc is polling and waiting, all Requests sent to the
> Server with
> the 1.Rpc are
> received and replied by the Server, received by the Browser but the
> Response
> handler (defined when executing the callAsync method) is NOT executed.
Hi,
I have a Application which needs fast communication to the Backend Server.
So I made two qx.io.remote.Rpc() Objects:
The 1. Rpc is used for sending Request Objects to the Server.
The 2. Rpc is for receiving Reply Objects from the Server. Its a 'long
Polling' strategy, the Rpc Request on the
