rpc

Is it appropriate to use message queues for synchronous rpc calls via ajax

为君一笑 提交于 2020-01-02 01:21:46
问题 I have a web application that uses the jquery autocomplete plugin, which essentially sends via ajax a request containing text that has been typed into a textbox to our web server, once the web server receives this request, it is then handed off to rabbitmq. I know that we do get benefits from using messaging, but it seems like using it for blocking rpc calls is a misuse and that something like WCF is far more appropriate in this instance, is this the case or is it considered acceptable

Java RMI与RPC的区别

安稳与你 提交于 2020-01-01 09:03:21
文章转自http://www.cnblogs.com/ygj0930/p/6542811.html 一:RPC 远程过程调用 RPC(Remote Procedure Call Protocol)远程过程调用协议,通过网络从远程计算机上请求调用某种服务。 一次RPC调用的过程大概有10步:   1.执行客户端调用语句,传送参数   2.调用本地系统发送网络消息   3.消息传送到远程主机   4.服务器得到消息并取得参数   5. 根据调用请求以及参数执行远程过程(服务)   6.执行过程完毕,将结果返回服务器句柄   7.服务器句柄返回结果,调用远程主机的系统网络服务发送结果   8.消息传回本地主机   9.客户端句柄由本地主机的网络服务接收消息   10.客户端接收到调用语句返回的结果数据 二:RMI 远程方法调用 RMI:远程方法调用(Remote Method Invocation)。能够让在客户端 Java 虚拟机上的对象像调用本地对象一样调用服务端java 虚拟机中的对象上的方法。 RMI远程调用步骤: 1,客户调用客户端辅助对象stub上的方法 2,客户端辅助对象stub打包调用信息(变量,方法名),通过网络发送给服务端辅助对象skeleton 3,服务端辅助对象skeleton将客户端辅助对象发送来的信息解包,找出真正被调用的方法以及该方法所在对象 4

Why does NFS use UDP by default?

别等时光非礼了梦想. 提交于 2019-12-31 17:54:20
问题 I'm sure there's some ancient legacy reason for it, but what is it? It seems like a service that's geared towards reliable data delivery. 回答1: NFS was originally designed to be used on a LAN where loss rates are very low. UDP is faster, and has less overhead NFS is stateless, so it's simple for clients to retry Note that NFS v3+ can use TCP. 回答2: UDP is the default for NFSv2 (which nobody should really use these days) but NFSv3 use TCP by default. TCP mounts are more reliable and you know you

MessagePack: fast cross-platform serializer and RPC - please share experience

偶尔善良 提交于 2019-12-31 13:13:18
问题 Looking for some fast, simple and stable RPC library I stumbled upon MessagePack project which seems to be very good. It is also under active development. If you used it in any way, could you please share your experience? P.S. I think this question should be community wiki 回答1: Well, after some time I found that MessagePack is not well-documented (there was even non-working tutorial in Wiki for Java), there are like 7 outstanding bugs several months old without any replies. Code even is not

MessagePack: fast cross-platform serializer and RPC - please share experience

纵然是瞬间 提交于 2019-12-31 13:13:12
问题 Looking for some fast, simple and stable RPC library I stumbled upon MessagePack project which seems to be very good. It is also under active development. If you used it in any way, could you please share your experience? P.S. I think this question should be community wiki 回答1: Well, after some time I found that MessagePack is not well-documented (there was even non-working tutorial in Wiki for Java), there are like 7 outstanding bugs several months old without any replies. Code even is not

What RPC module should I use to implement RCP in Python and be able to change connection method later?

◇◆丶佛笑我妖孽 提交于 2019-12-31 05:30:50
问题 I do have to implement some RPC from Python to Python but the connection methods are quite limited for security reasons. Currently it seems that I may be able to connect using SSH and run a single python script on the remote system. This can change in the future when we may have to connect using something else, maybe telnet so I would like a solution that can work using different protocols. Another potential limitation is regarding Python version, it has to work with Python 2.5-2.7 even if

gwt java.lang.ExceptionInInitializerError

╄→гoц情女王★ 提交于 2019-12-31 04:30:10
问题 I'm working on a GWT app, and keep getting the error shown below. I followed the GWT tutorial regarding naming conventions for servlet classes, and followed the Service / Async / ServiceImpl structure. I also tried adding the -XX:-UseSplitVerifier VM argument to fix a previous problem. any ideas on what's going on? SEVERE: javax.servlet.ServletContext log: Exception while dispatching incoming RPC call java.lang.ExceptionInInitializerError at sun.reflect.NativeConstructorAccessorImpl

SSL certificate problem in a web service proxy

萝らか妹 提交于 2019-12-31 02:42:06
问题 I am building a JAVA web service client in which i connect to a service. This service has a ssl certificate verification. How to call this service using ssl certificate verification. I am using JAX-RPC implementation in client built using Eclipse. An example would be appriciated. 回答1: I am able to do the web service connection... I added the key store using the command: keytool -import -trustcacerts -file <file path/filename.cer> -alias <aliasName> -keystore <JAVA_HOME/jre/lib/security

微服务之集成(四)

风流意气都作罢 提交于 2019-12-31 01:38:34
1. 寻找理想的集成技术 微服务之间通信的方式的选择非常多样化,但哪个是正确的呢?SOAP ? XML-RPC ? REST ? Protocol Buffers?后面会逐一讨论。 首先,我们要考虑的是,我们到底希望从这些技术中得到什么。 1.1 避免破坏性修改 有时候,对某个服务做的一些修改会导致该服务的消费方也随之发生改变。但是,我们希望选用的技术可以尽量避免这种情况的发生。 1.2 保证API的技术无关性 保证微服务之间的通信方式的技术无关性是非常重要的。这就意味着,不应该选择哪种对微服务的具体实现技术有限制的集成方式。 1.3 使你的服务易于消费方使用 消费方应该很容易的使用我们的服务。理想情况下,消费方应该可以使用任何技术来实现,从另一方面来说,提供一个客户端库也可以简化消费方的使用。但是通常这种库与其他我们想要得到的东西不可兼得。例如,使用客户端库对于消费方来说很方便,但是会造成耦合的增加。 1.4 隐藏内部实现细节 我们不希望消费方与服务的内部实现细节绑定在一起,因为这会增加耦合。所以,所有倾向于暴露内部实现细节的技术都不应该被采用。 2.为用户创建接口 3.共享数据库 目前业界最常见的集成形式应该就是数据库集成了。使用这种方式时,如果其他服务想要从一个服务获取信息,可以直接访问数据库。如果想要修改,也可以直接在数据库中修改。 这种方式看起来非常简单

RPC frameworks available?

徘徊边缘 提交于 2019-12-30 01:13:07
问题 I am looking to use a RPC framework for internal use. The framework has to be cross language. I am exploring Apache Thrift right now. Google protocol Buffers does not provide RPC capabilities exactly. What are the choices I have got apart from Thrift. (my servers will be primarily Java and the clients will be Java, Python, PHP). 回答1: There is also MessagePack which claims to be faster than Protocol Buffers and have more features than Thrift. 回答2: I would look at REST as a first option because