Thanks Thomas. I was hoping it'd be easier and I was just missing something. Moving this call out of rpc is probably the best solution. Thanks again for the guidance!
Since servlets 3 had been out for a long time now it'd be a great idea to have the developers write this feature into RemoteServiceServlet. On Friday, December 23, 2016, Thomas Broyer <[email protected]> wrote: > GWT RPC has been thought of as blocking on the server side. Making it > async would require changes to the RemoteServiceServlet: most likely the > method would be async just like on the client side with the implementation > calling the callbacks onSuccess or onFailure. > > Your best bet here would be to write a RemoteServiceAsyncServlet by > copying from RemoteServiceServlet, hoping for all underlying APIs to be > public. > Either that or move off of RPC for that call (future proof) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "GWT Users" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/google-web-toolkit/-eITQalAc9k/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected] <javascript:;>. > To post to this group, send email to [email protected] > <javascript:;>. > Visit this group at https://groups.google.com/group/google-web-toolkit. > For more options, visit https://groups.google.com/d/optout. > -- 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/google-web-toolkit. For more options, visit https://groups.google.com/d/optout.
