On Wednesday, June 10, 2015 at 12:21:03 PM UTC+2, Anton Mityagin wrote: > > In general, it is unclear why the guys at Google have made the RF this way. >
If you look at the changes between the various milestones and RCs of GWT 2.1, and then 2.1.1 and 2.2, you'll see that RF is totally different today than it was initially conceived (TL;DR: started as just CRUD & keeping the client and server entities in sync, evolved into RPC). Unfortunately, some early design decisions have slept in, making things a bit blurry about what RF is best at. I also believe the "partnership" with Spring Roo at the time wasn't for the better (and it didn't last long, I'm not even sure it lived 'til the 2.1 final release). But there are many things RF does quite well: RPC (with ValueProxy), “patching” entities in client→server communications (but without optimistic locking), batching (soon to be obsoleted by HTTP/2 though), support for non-XHR transports (e.g. WebSocket, though I haven't seen any such implementation), support for non-GWT environments, and the lose coupling between client and server making it a valid choice for e.g. mobile (Android) or offline-capable apps, where the client is hard to keep in sync with the server. -- 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/d/optout.
