hessian vs burlap

First, the summaryThis paper compares the transmission performance of 5 kinds of communication protocols such as Rmi,hessian,burlap,httpinvoker,web service in different data structures and different data volumes. RMI is the Java language itself provides the communication protocol, stable and efficient, is the basis of EJB. However, it can only be used for communication between Java programs.

This article mainly introduces two cases, the first is to use Hessian to implement the remote procedure call, the second is the binary RPC protocol provided by Hessian and the servlet for data interaction, Hessian itself is an HTTP-based RPC implementation.Case one:1. Preparatory workHere you build a MAVEN project that contains four modules, the parent module (on

Turn from:http://lancui.iteye.com/blog/935578Brief introductionSimpler and faster than Webservice,hessian. The Binary RPC Protocol (binary) is used because the binary protocol is used, so it is well suited for sending binary data. Hessian is typically serviced through a Web application, so it is very similar to webservice. It's just that it doesn't use the SOAP protocol.Hessian provides remote services thro

Hessian Study Summary (i)--hessian introductionFirst,the fundamentals of remote communication ProtocolsNetwork communication needs to do is to transfer the stream from one computer to another computer, based on the transport Protocol and network IO to achieve, where the transport protocol is more famous HTTP, TCP, UDP and so on, HTTP, TCP, UDP are based on the concept of Socket for a certain type of applica

Spring currently provides integration of remoting technologies such as RMI, Httpinvoker, Hessian, burlap, and WebService. Spring masks the differences in these implementation technologies by simply developing a simple Java object (Plain old Java Objects,pojo) and then writing the configuration file in the format set by spring. A comparison of several remoting implementations The remoting implementation tech

Java learning path-Hessian learning, java path-hessian Hessian is a lightweight HTTP-based remote service solution. Hessian, like Rmi, uses binary messages for client-to-server interaction. However, unlike other binary remote calling technologies (such as Rmi), binary messages can be transplanted to other non-Java lang

, which aggregates the Java serialization and Java Remote Method Protocol (Java Protocol). He can be seen as the Java version of RPC, because traditional RPC does not apply well to distributed object systems. Java RMI supports communication between program-level objects stored in different address spaces, enabling seamless remote calls between remote objects. He also has its shortcomings, he can only through the RMI protocol access can not be accessed through the HTTP protocol, unable to penetra

well to distributed object systems. Javarmi, however, supports communication between program-level objects stored in different address spaces, enabling seamless remote calls between remote objects. He also has its shortcomings, he can only through the RMI protocol access can not be accessed through the HTTP protocol, unable to penetrate the firewall.There is also a remote invocation method that is Httpinvoker: He also groups and deserializes parameters and return values through the Java seriali

well to distributed object systems. Javarmi, however, supports communication between program-level objects stored in different address spaces, enabling seamless remote calls between remote objects. He also has its shortcomings, he can only through the RMI protocol access can not be accessed through the HTTP protocol, unable to penetrate the firewall.There is also a remote invocation method that is Httpinvoker: He also groups and deserializes parameters and return values through the Java seriali

distributed object systems. Java RMI supports communication between program-level objects stored in different address spaces, enabling seamless remote calls between remote objects. He also has its shortcomings, he can only through the RMI protocol access can not be accessed through the HTTP protocol, unable to penetrate the firewall.There is also a remote invocation method that is Httpinvoker: He also groups and deserializes parameters and return values through the Java serialization mechanism,

version of RPC, because traditional RPC does not apply well to distributed object systems. Java RMI supports communication between program-level objects stored in different address spaces, enabling seamless remote calls between remote objects. He also has its shortcomings, he can only through the RMI protocol access can not be accessed through the HTTP protocol, unable to penetrate the firewall.There is also a remote invocation method that is Httpinvoker: He also groups and deserializes paramet

; Httpinvoker >= hessian>>burlap >> WebService RMI is Java-brought with limitations and is limited to remote access between Java programs. Httpinvoker uses the Java serialization technology to transfer objects, which are essentially the same as RMI, and are equally similar in terms of efficiency. The lowest efficiency is webservice, why there are a large number of people in use. Because the XML document is

Project selected Hessian as the implementation of the Web service, is indeed very lightweight, and the speed of the same as directly with the socket, all is binary transmission save a lot of overhead. However, in the use of the business need is to obtain the remote IP address, host name and other information. Turn Hessian documents and Google the N times did not, forced to Caucho and spring forum to ask, ha