Re: Is moving away from RPC a good idea?

Finally I've decided to stick to RPC and use gwt-servlet-jakarta. We will have a lot of applications (50+) to migrate to jakarta at some point, this will be the fastest way.

Thanks all for your comments.

On Mon, 15 Jan 2024 at 11:26, Jens <jens.nehlmeier@gmail.com> wrote:

Some mention "some annoying downsides" or "is imperfect in a lot of ways" regarding gwt-rpc. What are does?

1. Client and server always need to be in sync because of serialization policy. So a user must reload the web app if you redeploy your application and have modified shared classes. 

2. If you want to use J2CL in the future you should not use it.

3. You can only use it with GWT clients unless you reimplement the wire format in other languages / applications. Only unofficial information about the wire format exists. 

4. No async servlet support

5. Command pattern doesn't work well with GWT-RPC because you cannot code split the client side serialization data. So your initial or leftover fragment contains everything that goes over the wire. Code splitting only works well if you have one GWT-RPC service per code split condition.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/cc4b2a17-a072-4685-b138-34f31e46cc5fn%40googlegroups.com.

--
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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABi7_98Pk%2BobtN2SiychHVx1sKpjqHW70-XH3pMXQ5pXgqTfQg%40mail.gmail.com.