Re: RPC AsyncCallback freezes chrome

You say you have many other RPC calls etc.

Since a few RPC calls can be active in parallel, some may return with a response before others….

It could be one of the other RPC calls is causing the problem perhaps the code is in an endless loop.  So the browser can never respond to the AsyncCallback  that you suspect is not getting a response.

Mike.

On Saturday, July 6, 2013 3:22:12 AM UTC-10, fenyoapa wrote:

Ok, then I don't understand what do you mean on "isolate your problem in a stand alone gwt app". I can provide short code snippets (as I did above) but I can't provide a working gwt app with which the problem can be seen because of the points I wrote. Or, maybe I can package the whole app and send, but I guess you don't thought that. Can you please help me how to help you in order to you will be able to help me...

2013. július 6., szombat 14:31:42 UTC+2 időpontban Ed a következőt írta:

> Sorry I can't, It runs behind a VPN in a special environment and it is property of our customer..

Why not?

I just make your own gwt app that shows the issue....  (no client code, no vpn).

I don't understand what this has to do with vpn or customer code?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.