I'd recommend request factory. The issues with rpc are: * rpc strongly couples your client and server, so you face invocation exceptions every time you deploy a server side change. RF on the other hand is a protocol, not an RPC API. * generator bakes every subclass of your objects on the client. That means you have to be very careful with what types you use / are in the classpath when you compile. With RF you only have what you want, you're in complete control. * batch requests are baked into the RF protocol, you don't have emulate them with "dto containers". Plus you can easily change your mind at any time, and also possibly batch things from independent components (loose coupling ftw)
Sure RF has a steeper learning curve but I believe you win in the long term. I'd suggest you upgrade to 2.5 as soon as its released though: many fixes to RF are coming. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/3xj5_VbmPRUJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
