I consider this as the biggest advantage: you keep type-safety across client/server calls. If you do some breaking changes, the compiler will tell you! I definitely prefer this above finding out at runtime… You can always achieve higher levels of flexibility by adding abstraction layers between between hour client and server code - without loosing strict type checking.
Rogelio Flores <[email protected]> schrieb am Mo. 23. Mai 2022 um 19:37: > The big disadvantage that I see with gwt-rpc is that it ties your > client-side with your server-side code (if you change anything related to > your models/rpc on the client side, you also have to update your serve-side > code, otherwise, it will not work). To me that in itself is a big > disadvantage. With something like REST APIs, your client and server side > code remain decoupled, giving you more freedom. > > On Friday, May 20, 2022 at 8:14:58 AM UTC-6 [email protected] wrote: > >> why not use gwt-rpc? I am a lazy guy and am happily using it for more >> than 10 years now - I even use the generated serializers in combination >> with WebSockets. What can possibly go wrong here...? >> >> On Fri, May 20, 2022 at 3:57 PM Thomas Broyer <[email protected]> wrote: >> >>> Short answer: don't start using RequestFactory now, it's been >>> practically unmaintained for years. >>> >>> Long answer: there's not really a longer answer actually, it's OK to >>> keep using RF in existing projects (if you can't afford moving to something >>> else), but don't start anything with it now. >>> (I wouldn't start anything new with gwt-rpc either BTW, but YMMV) >>> >>> On Friday, May 20, 2022 at 12:32:18 AM UTC+2 hprc wrote: >>> >>>> I know that GWT Request Factor plays an important role in Java object >>>> persistence and communication between client and server. >>>> However, on the server and client, even one object needs to generate >>>> related classes and interfaces, and then annotation settings etc. need to >>>> be set for each class and interface. >>>> It is complicated and has a lot of trouble to create. >>>> >>>> Originally, these things are like plugins, and it is desirable to >>>> select one object and generate a related class, but do you all know? >>>> >>>> I have been using GWT for over 10 years, but I do not use >>>> "RequestFactory" and operate only with objects like Map by RPC >>>> communication. >>>> This can simplify the entire system and greatly reduce the effort >>>> required to create it. >>>> >>>> GWT RequestFactory >>>> https://www.gwtproject.org/doc/latest/DevGuideRequestFactory.html >>>> >>> -- >>> 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 view this discussion on the web visit >>> https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com >>> <https://groups.google.com/d/msgid/google-web-toolkit/66b91749-8cb7-4b84-964d-82c2996adca8n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >> -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit/e3334aae-7ad4-49d9-8644-c2b6cfe9f065n%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit/e3334aae-7ad4-49d9-8644-c2b6cfe9f065n%40googlegroups.com?utm_medium=email&utm_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACwwWxO9yB8OapamsQDx9yCtxu0T3Mwnaa0KRuXP0uf__rjdVw%40mail.gmail.com.
