Thanks Thomas, I think I get what RequestBatcher does. We do the same but just passing around the RequestContext...
Seems like I wasn't making life difficult by mistake. Sort of a relief. I've asked permission to share our code. I've a horrible feeling it will get stuck with the lawyers. Many thanks Sam On Friday, July 12, 2013 12:25:11 PM UTC+1, Thomas Broyer wrote: > > > > On Friday, July 12, 2013 12:18:36 PM UTC+2, salk31 wrote: >> >> Sadly I've looked at the source quite a few times. >> >> Can it be used for our use case (Send contents of the Editor to the >> server multiple times and perform different service methods each time)? >> > > No. RequestBatcher only manages the lifecycle of a RequestContext (create > one if we don't have one, then schedule a command at the end of the "event > tick" that will fire() the RequestContext and immediately forget about it), > really nothing more. > > We got stuck as we could only add (not remove) Requests to the >> RequestContext. >> >> The code looks to me that if a Request is a success or failure then it >> shuts down the RequestContext? So RequestContext doesn't fail but is shut >> down. AbstractRequestContext:409 ? >> > > Yes. RequestContexts can only be used once, unless there are constraint > violations, a transport failure (network error) or a general failure (that > one should be very rare). > -- 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.
