And +1 to everything Matthew already said.
http://gwt-code-reviews.appspot.com/1875803/diff/1/user/src/com/google/gwt/http/client/RequestImpl.java
File user/src/com/google/gwt/http/client/RequestImpl.java (right):
Thanks for the feedback!
On 2012/12/13 19:36:01, mdempsky wrote:
Thanks for the patch. If you don't mind, could you try uploading the
next
revision to Gerrit insead? See instructions at:
https://groups.google.com/d/msg/google-web-toolkit-contributors/fmHDlsnfdEQ/fc6lvNdxROQJ
If that
On Thursday, December 13, 2012 5:31:28 AM UTC+1, Ray Cromwell wrote:
How would you deal with re-entrancy though, e.g.
Java - JS - Java - JS
If you simulate a synchronous call from JS to Java by breaking, what
happens when Java calls back into JS? Everytime I thought about doing
this,
Thanks for the feedback.
http://gwt-code-reviews.appspot.com/1875803/diff/1/user/src/com/google/gwt/http/HTTP.gwt.xml
File user/src/com/google/gwt/http/HTTP.gwt.xml (right):
http://gwt-code-reviews.appspot.com/1875803/diff/1/user/src/com/google/gwt/http/HTTP.gwt.xml#newcode31
On 14/12/12 11:24, Thomas Broyer wrote:
and there's also the issue with GWT-RPC serialization policies that make
using SuperDevMode tricky (apparently, I don't use RPC).
Tricky is too strong a word for it. It only takes a small amount of code, so
that the RPC servlet's
