To answer the original question, no - no changes are planned in the Xsrf
variants of generator-based RPC. We should remove those comments. I am
aware of no reason to not use the Xsrf variants in production code.
Looking forward, beyond gwt-user.jar, I have the core of RPC working
correctly in
Sorry I lost my context in user groups - didn't notice this was external
group.
What I sent was just for Google internal usages; pls ignore my message.
On Tue, Oct 31, 2017 at 2:52 PM, 'Jonathan Nieder' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:
> Is there a
Is there a public announcement equivalent to [1] for external users to read?
вт, 31 окт. 2017 г. в 14:47, 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com>:
> They are not going to change and plenty of people use it for production
> but there is a bigger
They are not going to change and plenty of people use it for production but
there is a bigger issue:
GWT-RPC is deprecated and in maintenance mode for over 2 years now [1].
[1]
https://groups.google.com/a/google.com/d/topic/gwt-announce/RjxACk-nJYI/discussion
On Tue, Oct 31, 2017 at 4:51 AM,
Gwt Documentation as well as GWT IN action recommend extending
XsrfProtectedService on client side and XsrfProtectedServiceServlet on
server side
But both thse methods are still marked as "EXPERIMENTAL and subject to
change. Do not use this in production code."
What gives? is this a
