Although I also think that this may be a bad workflow problem, I also think that for some use cases this patch might be helpful.
For me, this problem appears in two cases. Case 1. A reporting app which loads reporting data for a long period and allow client side analysis. The request load ~5mb (compressed is less than 600k). In this case I admit that a re-think is the best solution because requestfactory it's really bad loading bulk data. Request-factory its perfect for editor framework or similar graph data request, but it's not useful for bulk ValueProxy data loading. Case 2. A translation tool which loads all translations to allow offline editing. This request load a ~1mb (1500 keys with per-language translation and metadata). This request is done in the the first time an user login, but most of the time this data is loaded from the local storage, so I think that this use case must be supported by request-factory. With this patch, this works fine, without this patch, usually this first load usually fires the 'slow script' popup. On Tuesday, July 8, 2014 6:36:09 PM UTC+2, Jens wrote: > > 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 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/35308efb-b4d7-42c6-b261-977a0480aa89%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.