问题描述
与AJAX调用相比，GWT（Google Web Toolkit）的RPC（远程过程调用）对于从浏览器/ javascript到服务器的异步操作是不同的还是SIMILAR？如果他们不同，有人可以帮我理解他们有什么不同吗？
我还听说这个RPC实现不适用于所有的Server容器。例如，GWT项目在Apache Tomcat中不起作用。另外，这个RPC是一个Google的自定义实现，还是标准的实现？
$ b
1）GWT RPC 使用AJAX 来允许GWT应用程序进行数据传输。
$ b 2）GWT RPC提取出大量信息并包装ajax，使您可以在JAVA中编写代码而无需担心不同的浏览器。
3）它在tomcat，jetty和每个服务器容器中 。在某些情况下，人们错误配置路径（开发模式与生产模式导致图像路径/ css混淆）。b） >
How is GWT (Google Web Toolkit)'s RPC (Remote Procedure Call)'s for Asynchronous operations from browser/javascript to server is DIFFERENT or SIMILAR when compared to the AJAX calls ?
If they are different, could someone help me understand how they are different ?
I also heard that this RPC implementation does not works with all Server containers. For example, the GWT project did not work in Apache Tomcat.
Moreover, is this RPC a an custom implementation of Google , or is it a standard implementation ?
1) GWT RPC uses AJAX to allow Data transfer for GWT applications.
2) GWT RPC abstracts out lot of information and wraps ajax to allow you to code in JAVA without worrying about different browsers.
3) It WORKS in tomcat, jetty and in every server container. In some cases people misconfigure the paths ( dev mode vs production mode causes confusion in image paths/ css)
4) RPC is indeed a CUSTOM implementation from Google.
这篇关于GWT的RPC与AJAX不同吗？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！