Comments on: Java Remoting: Protocol Benchmarks

By: The Zenbi Architecture | Zenbi

The Zenbi Architecture | Zenbi — Sat, 20 Aug 2011 23:20:26 +0000

[...] instances is much faster too. These are two charts depicting the speeds of the various protocols (source). SOAP can be compared to XML-RPC. Clearly, RMI is superior (click to enlarge): Also [...]

By: Java Remoting « Java Mania

Java Remoting « Java Mania — Mon, 11 Apr 2011 10:11:22 +0000

[...] ya tiene algunos años y las librerías y las JVMs han ido mejorando, sobre todo en rendimiento, este estudio es ilustrativo en términos comparativos sobre los tiempos de respuestas de diferentes tecnologías [...]

By: Kam

Kam — Wed, 23 Jun 2010 18:25:41 +0000

Hello,

Does anyone knows how does Hessian manage the HTTP connections? Is it using a pool of connections or it creates a new one for each new request?

I have not luck with google so far

Thanks!
Kam

By: Kallin Nagelberg

Kallin Nagelberg — Tue, 27 Apr 2010 20:28:29 +0000

I was recently required to start writing services using RMI instead of RESTful JSON transfer and wrote a little tutorial on how to support both automatically in Grails, http://techscursions.blogspot.com/2010/04/easy-rmi-services-in-grails-with-json.html . Enjoy!

By: Kari’s World » Blog Archive » Custom RMI?

Kari’s World » Blog Archive » Custom RMI? — Sun, 22 Nov 2009 18:16:42 +0000

[...] Update 22.11.2009 Wireless Java RMI Efficient Support of Java RMI over Heterogeneous Wireless Networks Wireless Optimization for Java RMI Java: Expected overhead of the rmi protocol Java Remoting: Protocol Benchmarks [...]

By: Performance Considerations in Distributed Applications Performance, Scalability and Architecture – Java and .NET Application Performance Management (dynaTrace Blog)

Tue, 29 Sep 2009 23:26:39 +0000

[...] are using SOAP as an RPC protocol although there are no advantages in following this approach. Measurementshave shown that the overhead of SOAP compared to RMI-JRMP is significant. Performance degradation by [...]

By: |>> Burlap

|>> Burlap — Thu, 24 Sep 2009 21:42:23 +0000

[...] Verwendung2 Siehe auch zu “>Weblinks zu zu Burlap Design NotesJava Remoting: Protocol Benchmarks, Performancevergleich von Daniel Gredler zwischen Hessian, Burlap, Oracles ORMI, RMI, XML-RPC [...]

By: Brian Bonner

Brian Bonner — Thu, 18 Jun 2009 20:36:05 +0000

I’m curious have you been able to stream complex objects across the wire with burlap, hessian or hessian2, Strings seem to work fine, but any complex user defined objects seem to fail.

By: Chris

Chris — Thu, 28 May 2009 12:10:14 +0000

Nice piece of work! Again, thanks for sharing this information.

In case speed an excellent scaling behaviour is an issue, it would be indespensable to obey main semantic rules of the web – i.e. using GET where clients need a view to a centralized model and POST where clients change the model. GET requests meight be cached by clients and proxies, POST requests cannot.

As far as I can see, all the lightweight candidates (Hessian, Burlap, HttpInvoker) allways use POST, which means the whole HTTP Caching infrastructure is turned off.

Does anybody know a framework which uses HTTP, is leightweight AND offers to switch to GET where it is appropriate? (And, yes, I know it is a challenge to map method parameters to URL parameters.)

By: Mojahedul Hoque Abul Hasanat

Mojahedul Hoque Abul Hasanat — Tue, 12 May 2009 05:23:48 +0000

A very useful article. I was just looking for this information. Thanks for sharing.