On Mon, Mar 16, 2009 at 11:59 PM, Vitali Lovich <[email protected]> wrote:
> I'm not 100% sure if this is related to the patch, but I'm seeing an issue > in the following situation: > I doubt this has anything to do with the patch -- basically the issue is that with the plugin, Firefox is dependent upon the link to the OOPHM server since the plugin makes synchronous RPC calls from native code that block the UI event loop until it gets a response (since the calls to Java methods from JS and vice-versa have to be synchronous). If that connection goes away, it can hang the browser until the OS notices the connection has died. If your TCP connection goes to another machine, then the connection will be killed by the other end due to keep-alive being set, but the process running on the laptop won't notice for a while after it comes up -- but it should eventually come back. If both the OOPHM server and the browser are running on your laptop, I am surprised that there would be any issues here (though frequently after waking up everything has to be paged back in from disk so you can experience sluggish behavior while that happens), but this is not something that has been tested as far as I know. This is probably a good time to mention that OOPHM isn't the default because it has a lot of unpolished edges. If you aren't willing to put up with them or use workarounds (like closing the OOPHM session in your browser before suspending if that is causing an issue), then perhaps you shouldn't be using it until we get it more polished. We do want to know about issues such as these, but it will probably be a while longer before everything is the way we want it. -- John A. Tamplin Software Engineer (GWT), Google --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
