On Friday, July 12, 2013 11:48:56 AM UTC+2, salk31 wrote: > > Hi Thomas, > > I really do struggle with RequestBatcher sorry... However is it correct > that it uses a single RequestContext? and that if any Request in a > RequestContext is a success or a failure then the whole RequestContext is > locked? That is the basis I was working on. Be very glad (if feel a bit > foolish) if that is not the case. >
RequestBatcher only handles creation and firing of a RequestContext, whose lifetime is an "event tick". Go look at the code, it's rather straightforward. So yes, it only uses a single RequestContext. However, the success or failure of service methods are independent from each other. Only errors that cannot be attributed to a given service method call (i.e. network errors, creating the payload on the client-side, parsing it on the server-side, validating the domain objects, serializing them back, and parsing the response on the client-side) can cause the RequestContext to "fail" (either onFailure or onConstraintViolations). > NonAtomicBatch sends things over the same HTTP request but with multiple > RequestContexts. > How do you handle it on the server-side? I suppose you have a specific RequestFactoryServlet? -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/groups/opt_out.
