I built an app using GWT and GWT-RPC in 2011-2012, but am currently working on a clean-slate rewrite of the client using modern JS (ES6, React, Webpack, etc). I've opted to leave the existing client codebase entirely as-is, and have exposed my existing backend APIs over JSON-RPC as well. This is allowing me to make some pretty good progress on the new client without having to make significant changes to the backend or the existing client. It's also very nice to finally be able to examine my network calls in a browser debugger, and since JSON-RPC is language-independent, would also make it feasible to call those APIs in other contexts if I ever wanted to.
On Thursday, July 7, 2016 at 2:17:12 PM UTC-4, Gilberto wrote: > > When I first used GWT, I started using GWT RPC as the main communication > channel with the server. Years later, when I first needed a native mobile > application, and when I needed to expose API endpoints to partners to > integrate data with my services, I realized I should have gone RESTful from > day 1 - migrating from GWT RPC to a RESTful architecture was painful and > slow. > > GWT RPC is easy to implement and close to other Java communication > technologies (like RMI), but in my experience can create several problems > in the long term. > > Having said that, I'm always ok with options. GWT won't support GWT RPC in > the future, but nothing stops anyone from porting the current GWT RPC > mechanism to GWT 3. Of course several stuff would need to change (because > of the generators), but I'd imagine it's totally doable. > -- You received this message because you are subscribed to the Google Groups "GWT Users" 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 https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
