Re: GWT RPC call recognized as a Java Method Injection by Fortiweb

[Ralph Fiergolla]

That is, as long as I stay within GWT there is no need to change (and loose
type checking and convenience). I will happily stay with GWT RPC then!

R

Jens  schrieb am Mo. 24. Juli 2023 um 18:24:

>
> I think I asked the question before: as a long-term GWT-RPC user, what
> would be the benefit of moving to some other RPC protocol/mechanism?
>
>
> Depends on your situation of course. If you want to use your existing
> backend with other clients written in other languages then GWT-RPC is a bad
> fit. While the wire format of GWT-RPC is documented, you still need to
> write the client code to generate it. Also GWT-RPC supports inheritance
> which other languages you want to use might not support. Other JS based RPC
> solutions as well as general purpose solutions like gRPC typically do not
> support inheritance.
>
> GWT-RPC will already be annoying if you decide to have some portions of
> your app being written in a different framework since it is easier to find
> developers for that framework, e.g. angular, svelte, react, whatever. You
> would then need to define a JS api that calls into GWT code so these
> frameworks can talk to your GWT-RPC backend (or you need to provide new
> endpoints in your backend that do not talk GWT-RPC).
>
> -- J.
>
> --
> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/ab08b131-3904-49b1-8920-b924c7b31c9an%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACwwWxPMRKL%2Bk%3DBK-0P-e5xxykonSp7PAvMU0yQZdf1U6nzf6A%40mail.gmail.com.

Re: GWT RPC call recognized as a Java Method Injection by Fortiweb

[Jens]

I think I asked the question before: as a long-term GWT-RPC user, what 
would be the benefit of moving to some other RPC protocol/mechanism?


Depends on your situation of course. If you want to use your existing 
backend with other clients written in other languages then GWT-RPC is a bad 
fit. While the wire format of GWT-RPC is documented, you still need to 
write the client code to generate it. Also GWT-RPC supports inheritance 
which other languages you want to use might not support. Other JS based RPC 
solutions as well as general purpose solutions like gRPC typically do not 
support inheritance.

GWT-RPC will already be annoying if you decide to have some portions of 
your app being written in a different framework since it is easier to find 
developers for that framework, e.g. angular, svelte, react, whatever. You 
would then need to define a JS api that calls into GWT code so these 
frameworks can talk to your GWT-RPC backend (or you need to provide new 
endpoints in your backend that do not talk GWT-RPC).

-- J.

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/ab08b131-3904-49b1-8920-b924c7b31c9an%40googlegroups.com.