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 google-web-toolkit-contributors+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/a369ec0c-21c9-45aa-8b5f-23d595fd4eed%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
