gwt-rpc vs休息...它真的是一个或另一个？ [英] gwt-rpc vs rest... is it really one or the other?

问题描述

我有一个GWT客户端使用GWT-RPC来调用我的REST服务。为什么有些评论会将GWT-RPC与REST混为一谈，就好像你必须选择其中一个一样？我在客户端上使用了两个GWT-RPC，它们都是REST服务。我想用一个替代和沟渠GWT-RPC。为什么？这是SLOW（与我的Flex客户端达到相同的服务相比）。我检查了RestyGWT，但它的优秀文档（讽刺）使我听起来像需要构建RestyGWT客户端可以访问的RestyGWT服务。吉兹，谢谢。我的服务完成了。我真的不想碰它。所以听起来像一种可能的选择是从我的服务中生成一个客户端库，并将其用于我的GWT客户端以及RequestBuilder，以处理JSON到Java对象的编码/解码（并希望获得改进的性能）。如果这不能削减它，下一个选择是完全抛弃GWT。

解决方案

查看 Errai JAX-RS 与GWT-RPC一样容易构建REST客户端。 b $ b

I have a GWT client using GWT-RPC to make calls to my REST service. Why do some of these comments pit GWT-RPC against REST, as if you have to choose one or the other? I'm using BOTH... GWT-RPC on the client, which hits a REST service. I want to use an alternative and ditch GWT-RPC. Why? It's SLOW (compared to my Flex client that hits same service). I checked out RestyGWT but it's great documentations (sarcasm) makes it sound like I need to build a RestyGWT SERVICE that my RestyGWT client can hit. Geez, NO thanks. My service is done. I really don't want to touch it. So it sound like one possible alternative is to generate a client lib from my service and use it in my GWT client along with RequestBuilder to handle encoding/decoding of JSON to java objects (and hopefully get improved performance). If that doesn't cut it, the next alternative is to ditch GWT altogether.

解决方案

Have a look at Errai JAX-RS to build "REST" clients (almost) as easily as with GWT-RPC.

这篇关于gwt-rpc vs休息...它真的是一个或另一个？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！