Re: What was Direct-Eval RPC, and why didn't it work ?
It had a dependency on the Sun JVM (specifically it used sun.misc.Unsafe) There were some plans for a workaround, but for whatever reason TPTB decided to work on RequstFactory instead. You can get the same speed advantages with RF but there is a whole lot more boilerplate code needed (which in turn can be alleviated with DI and down the rabbit hole you go).* * -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/kxodM6RPKPkJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
What was Direct-Eval RPC, and why didn't it work ?
The documentation mentions a feature called Direct-Eval RPC[1], saying it didn't work as planned, and is now discouraged. What was it, and why is it now considered a bad idea ? [1]: http://code.google.com/webtoolkit/doc/latest/DevGuideServerCommunication.html#DevGuideDeRPC -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/_ZrS2K54DDgJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
