https://groups.google.com/d/topic/google-web-toolkit/p78CcdwsV3A/discussion
Was my post asking if there was away to avoid doing our own version of batching. On Monday, March 4, 2013 1:48:16 PM UTC, salk31 wrote: > > Hi Thomas, > > Unless I'm misunderstanding you I don't think what you suggest will work > for what we are doing. We want to send the contents of the form to the > server multiple times and call methods in our middle tier. > > The only way we could find to re-send the request attached to a form was > to fail validation, which would mean that service methods would not be > called. > > That make any sense? > > Regards > > Sam > > On Monday, March 4, 2013 10:28:54 AM UTC, Thomas Broyer wrote: >> >> >> >> On Monday, March 4, 2013 11:02:00 AM UTC+1, salk31 wrote: >>> >>> Thanks Thomas, >>> >>> Lots to look at there. >>> >>> So I can send multiple RF requests over a single HTTP request (to send >>> the contents of an Editor/RF tree multiple times, for validation) I have a >>> nasty Transport.startBatch(String name) method. I have been wondering about >>> marking the request somehow so I don't have to be so careful about using >>> try/finally to clear any nasty state after an error. Still feels wrong >>> assuming single threaded ;) >>> >> >> Batching comes for free with RequestFactory (call several methods on your >> RequestContext before you fire(), and combine several RequestContext in the >> same "batch" using RequestContext#append()); see also RequestBatcher to >> automatically fire() using a scheduleFinally (that's about moving the >> responsibility of calling fire()) >> > -- 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?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
