Every Async impl on the client gets a serializer instance to go with it - crack open the generated code to see what it comes up with. It is possible to subclass the ServiceInterfaceProxyGenerator to provide your own custom subclass of ProxyCreator which instead of setting the impl's superclass as RemoteServiceProxy would use some other impl of your devising. If I remember correctly, doInvoke can be overridden to pass off to some other class of your choosing, instead of sending data through the RequestBuilder. This is pretty easy to do, once you see how it all wires together, but it can take some time to learn. Additionally, this is something the GWT app would need to initiate – the RPC stuff doesn't work for the server to call the client.
Another option you might look into would be the AutoBeanCodex, used in AutoBean and RequestFactory stuff. -Colin -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
