incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <>
Subject [Incubator Wiki] Update of "JaffreProposal" by AlexanderVeit
Date Wed, 08 Apr 2009 21:47:44 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The following page has been changed by AlexanderVeit:

  Few of them limit themselves to connect only Java VMs with Java VMs, but try to be platform
neutral. Platform neutrality often adds significant overhead to the development process, or
comes with performance and/or memory consumption penalties (see e.g. SOAP based web services).
On the other hand, RMI, as a Java-only technology, is often cumbersome to configure and to
- This seems to be enough justification for Jaffre that overcomes these limitations.
+ Jaffre overcomes these limitations, and has additional benefits:
+  * It is not invasive when deployed in a JVM. The only required dependency is the JRE itself.
+  * It uses POJOs as service implementation classes. Clients use proxys that implement the
POJOs interface to communicate with the server.
+  * It does not need fancy decoration stuff like annotations or XML configuration files.
+  * It promises to allow quite complex object graphs to be marshalled. In fact to be
is the only requirement for marshalled objects.
+  * Jaffre does not need supplementary services such as registries or mediation services.
+  * It is easy to use. A service that exposes a given POJO, together with a simple socket
connector can be set up in seven lines of code. A client that remotely calls the POJO's interface
can be set up with five lines of code.
  A simple benchmark may illustrate Jaffre's efficiency. 20000 remote calls of the interface

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message