On Mon, Oct 27, 2008 at 9:25 PM, Freeland Abbott <[EMAIL PROTECTED] > wrote:
> So yes, we can and should and I think have fixed the underlying problem. > But the point to this patch is that if I found one way to wedge testing by > making recordResultsAndGetNextMethod() throw an exception, latent for > however many releases until Brian stepped in it, are there other ways to > provoke that? And can we not hang silently if there are? > To be fair though, there are other ways to hang: a client could completely stop contacting the server for any number of events... network, machine crash, browser crash, page generates a dialog box. I don't see much value catching one specific potential failure point on the server vs. just fixing the specific NPE from the bad equals() implementation. --~--~---------~--~----~------------~-------~--~----~ http://groups.google.com/group/Google-Web-Toolkit-Contributors -~----------~----~----~----~------~----~------~--~---
