On Fri, Feb 11, 2011 at 09:11, nrg-b <[email protected]> wrote:
>
> So for example, I have two services A and B. The structure of the returned
> data from each is quite different ie easy to tell apart from debug output.
>
> If I invoke ServiceA then rpc.callAsync() returns an id of (say)10. When my
> serviceA handler is invoked the id is also 10 and the data is as expected
> eg
> JSONDataSetA.
>
> Likewise, if I invoke ServiceB then callAync() might return an id of
> (say)11. When my serviceB handler is invoked the id is also 11 and the data
> is as expected for service B eg JSONDataSetB.
>
> But if I invoke both services in quick succession one immediately after the
> other, then the expected datasets seem to get swapped!!!
>
> So to prolong the contrived example above :-
> - ServiceA handler gets called with JSONDataSetB, and
> - ServiceB handler gets called with JSONDataSetA
>
> As soon as I introduce a slight delay eg (several calls to console.log())
> between each rpc.callAsync() then the problem goes away. If I call each
> service in isolation then all works as expected.
>
Try running it in Firefox using Firebug, with and without your delay code.
You can use the "Net" tab to look at the values being sent and received,
which will clearly tell you whether the problem is on the client side or the
server side. The RPC code has been used for many a year without seeing this
problem (to my knowledge), so I don't immediately suspect it. In fact, my
test program for async requests in the RpcExample contrib tested exactly
this feature. That doesn't preclude the possibility of a bug, however.
Derrell
------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
