Comments on: Java Remoting: Protocol Benchmarks

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.

By: Juan

Juan — Tue, 21 Apr 2009 14:32:57 +0000

For updated bechmarks:
http://code.google.com/p/thrift-protobuf-compare/wiki/Benchmarking

By: Hessian Web Service Protocol - Hello World Example « Java and more …

Hessian Web Service Protocol - Hello World Example « Java and more … — Fri, 10 Apr 2009 10:05:01 +0000

[...] from Caucho is released under the Apache License 2.0. Hessian is well integrated into Spring and seems to perform well for version 3.2 (one year old!). An ORM tool which supports Hessian out of the box is [...]

By: Stefan Scheidt

Stefan Scheidt — Thu, 09 Apr 2009 19:53:28 +0000

Wouldn’t it be nice to make your test suite open source, e.g. on googlecode?

Stefan

By: Rich

Rich — Tue, 07 Apr 2009 20:18:46 +0000

contract = constrast