Hehe this is not a bad thing! Just means that now exists simpler solutions. I personally think that RF keeps track of object (the entity id) which add really a lot of complexity, at this point I think that the lib should include some kind of storage with remote synchronization because if not, the complexity just makes thing difficult with the "only" benefit of reducing transfer size. I also don't like the obscure encoding, not easy to debug, not compatible with changes in the model (sometimes). IMO RF was promising, but it's complexity do not justify its benefits. But the best thing to do is always an small project, and test each strategy, RF, RPC and Rest+Jackson, Rest+JsInterop. The last one has de benefit nowadays than is done almost everything in the browser natively without different code for different browsers.
El jue., 5 ene. 2017 15:01, salk31 <[email protected]> escribió: > :( > > > On Monday, December 26, 2016 at 2:11:35 PM UTC, Thomas Broyer wrote: > > +1 Do not start learning/using RequestFactory (or even GWT RPC I'd say). > Learn JsInterop and use json-based http APIs. > > -- > 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. > -- 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.
