Introducing JBoss Remoting
Subject:   This is a step backward?
Date:   2005-02-25 16:24:51
From:   b.eckenfels
For sure this is a simple (basic?) framework. However compared to the other lightweight technologies of jboss, this looks a bit too trivial. This is not about Object Invocation or Aspect Oriented development. It does not really feature POJO nor mobile/agent based computing. There is nothing about virtualization, and I miss the SOA based descriptive part?

It pretty much reminds of the already everywhere used interceptors of jboss and is not much different from Axis' handlers. So where is the big good news here?


Main Topics Newest First

Showing messages 1 through 1 of 1.

  • This is a step backward?
    2005-02-27 10:28:37  telrod [View]

    Think you're missing the main point, which is that it is simple... and yet still powerful. The framework provides many features, such as callbacks (sync & async), remote classloading, auto discovery, oneway calls, etc., which is beyond the scope of many of the similar frameworks, yet IMHO is much easier to use. The other strong point of this framework is that you won't necessarily have to change your code or move to a different framework because of environment requirement changes (i.e. you start out with socket based, but have to switch to http). With remoting, is just a configuration change (which is as simple as changing the url from starting with socket:// to http://).

    There are several projects within JBoss that are using JBoss Remoting since they get the previously mentioned features. One, for example, is JBoss AOP, which uses JBoss Remoting for remoting of POJOs.