Hi Bob/Bart, I must have missed some of those methods in RPCRequestBuilder when trying to figure out how to do the automated retries. It looks like we could extend this to override the default callback mechanism and capture the serialized payload, just as we do in my proxycreator changes. I'll go back to the drawing board and see if that will work.
Joe On Feb 26, 4:53 am, BobV <[email protected]> wrote: > > 1) Would people be interested in my proxycreator patch, for potential > > inclusion into gwt core? > > 2) Does request pooling sound like it's something that would be of use > > in general? Is this something the gwt team would be interested in > > working with? > > Why did you go with the approach of patching the generator, as opposed > to injecting a custom RPCRequestBuilder into the proxy object? If > this use case cannot be satisfied with RPCRequestBuilder, then its API > is insufficient. > > -- > Bob Vawter > Google Web Toolkit Team -- http://groups.google.com/group/Google-Web-Toolkit-Contributors
