configuring jxta is easy enough, what about specializations? this entry touches upon the optimizer interface and how one can inject specialized logic into the jxta configuration process.

The optimizer feature of ext:config allows one to register app specific configuration optimization logic via a simple and well defined interface that can also be manged via a Profile, ie declaratively. One can add or remove as many optimizers as relevant to the task at hand.

One such optimizer was the results of a discussion whereby it was suggested that it is more efficient to deregister RendezVous if one is going to use a Relay service. Taking that use case into consideration, here is the corresponding logic:

Implement an optimizer:

import net.jxta.ext.config.Configurator;
import net.jxta.ext.config.optimizers.BaseOptmizer;

public class EdgeOptimizer
   extends BaseOptimizer {
    public void optimize(Configurator configurator) {
       if (configurator.getRelays().size() > 0) {
           configurator.clearRendezVous();
       }
   }
}

Next up, register the newly created optimizer with the respective profile by adding the following information:

 ...
 <configuration>
   <optimizer class="net.jxta.ext.config.optimizers.EdgeOptimizer"/>
 </configuration>
</jxta>

Lastly, bind this profile to AbstractConfigurator and you have now taylored your JXTA configuration process.

When considering one's JXTA deployment requirements there are likely a few optimizations that will come in handy and by using the above process the task of specializing the configuration process is easily achieved and infinitely extensible.

The "configuration" support within the profile supports passing nested name-value parameters as well, as implemented with the default RelayOptimizer:

...
 <configuration>
   <optimizer class="net.jxta.ext.config.optimizers.RelayOptimizer">
     <property name="reflection.service.bootstrap">
       http://rdv.jxtahosts.net/cgi-bin/reflection.cgi?2
     </property>
     <property name="reflection.service.max_wait">7</property>
   </optimizer>
 </configuration>
</jxta>

MyJXTA :: use it - learn it - do it

Java == platform independence
XML == application independence
JXTA == network independence

Secure End-to-End Computing

in my ears: RadioHead/Kid A/Optimistic