Well in general I think its not a big issue to process the response in an async way, however it just moves your problem into the future. Your patch allows you to load more data from the server without blocking the browser. However sooner or later the browser will block again because you probably start loading even more data in the future and the chunks of work will become too large again. But a maintainer of RequestFactory will decide if its worth it.
IMHO your real solution would be to rethink your UI / workflow so you don't need load such a large amount of data at once. Out of curiosity: How much data are you actually trying to transfer and which causes the browser to block? As a side note: GWT does not accept pull requests on GitHub. You must sign up on Gerrit and sign a CLA: http://www.gwtproject.org/makinggwtbetter.html#submittingpatches -- J. -- 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/9c5244f3-e55b-4ade-aa82-4c60e2294229%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
