Re: Requestfactory: How to use Object?

On Friday, January 6, 2017 at 1:11:35 PM UTC+1, Ignacio Baca Moreno-Torres wrote:

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.

FWIW, that was the original design, in the first milestones of GWT 2.1. It was overhauled in the RC (too complex I believe, particularly when requesting partial objects, meaning that your "local cache" could have some properties that are out-of-date, breaking the "diff" requests).

 

I also don't like the obscure encoding,

Much less obscure than RPC ;-)

And "documented" by AutoBeans: https://github.com/gwtproject/gwt/tree/2.8.0/user/src/com/google/web/bindery/requestfactory/shared/messages

They allow entities to be referenced multiple times without duplication, including reference cycles.

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.

I tend to agree. The main reason RF hasn't have more bugs fixed is that it's awfully complex (particularly on the server side) and hard to debug. I had floated the idea for years now to simplify things by generating code and relying less on reflection, but I'm not sure it'd be "compatible" with the ServiceLayer machinery.

 

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.

Most importantly, Web APIs put the complexity out of the code and into the protocol/API-design (to make it RESTful): they're super-easy to code on the both server (using Spring Web, JAX-RS, Restlet or RESTX) and client side (using JsInterop; which even allows your to share your objects –or interfaces– with the server)

If you're not too concerned with RESTful-ness and are happy with an RPC-style API, then JSON-RPC is quite easy to implement (and while RF can do JSON-RPC, it's not worth the complexity IMO)

And who knows, maybe one day we'll finally have grpc-web ;-)

--
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 google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.