Hi Jens, Thomas has tried to explain RequestBatcher to me but my understanding is that this essentially merges multiple RequestContexts.
One of our uses cases is to send the current contents of a form to the server then have the server generate a report on the latest state of that form. The user then goes on to just save that form as usual. If we used RequestBatcher wouldn't that mean the extra RequestContexts are attached for good? We have fiddled with the RequestTransport. I think our requirements are pretty generic though so worth having a community effort for an off the shelf solution? Cheers Sam On Friday, July 12, 2013 9:24:32 AM UTC+1, Jens wrote: > > Batching in RequestFactory can be done using RequestBatcher [1] and > retries, as well as sending status events about pending requests, can be > done by implementing a custom RequestTransport [2] for RequestFactory. Not > sure if there is anything pre-implemented in case of the RequestTransport > though. > > [1] > http://www.gwtproject.org/javadoc/latest/com/google/web/bindery/requestfactory/gwt/client/RequestBatcher.html > [2] > http://www.gwtproject.org/javadoc/latest/com/google/web/bindery/requestfactory/shared/RequestTransport.html > > -- J. > -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscr...@googlegroups.com. To post to this group, send email to google-web-toolkit@googlegroups.com. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
