Derrell Lipman wrote: > > 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. > Derrell >
Thanks, Derrell. I am encouraged to hear that the rpc code has been stable for a longtime with tests for this specific situation, as it means the problem will hopefully be my code ie I can fix it. I already use Firefox with Firebug. I've not used the Net tab so will give that a go. Thanks, once again. Bharat -- View this message in context: http://qooxdoo.678.n2.nabble.com/rpc-oddness-tp6015845p6015992.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ 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
