In this ignore white-diff is much more clear that I just wrap the end of the process in a callback - https://github.com/ibaca/gwt/commit/cd4901a23109c5350113363f2c539a8105e874b9?w=1
Also, I had tested this patch in a '1500 lines deobfuscator' application with no issue, although this patch can generate some silent ""concurrency"" problems that I had not detected yet. If I add this patch with some improvements and tests as a pull-request, it might be accepted? On Monday, July 7, 2014 3:00:53 PM UTC+2, Ignacio Baca Moreno-Torres wrote: > > RequestFactory has some performance problems. One of them occurs when the > AbstractRequestContext need to parse the response and create all proxies. > This problem is especially annoying if the time required to process this > response forces the explorer to show the warning message ~"*A script on > this page may be busy, or it may have stopped responding**".* > > I review the code and apply and alternative async execution which solves > the warning-popup problem (this is not a improve performance solution), but > I'm not sure if this simple solution may have some collateral problems. One > weird thing about the solution is that the EntityProxyChangeEvents might be > fired in different javascript loops, but this might be solved throwing this > event after all operations were processed. Is there any other problem? > > > https://github.com/ibaca/gwt/commit/cd4901a23109c5350113363f2c539a8105e874b9 > > I create this post to decide whether to create an issue (and patch) or not. > -- You received this message because you are subscribed to the Google Groups "GWT Contributors" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/4ee6a8ce-3925-4896-bc2e-81dea26ad8e6%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
