tbray has earned his jxta wings.

thing is, i suspect we can cut down the current jxta configuration class to 1/3 the size ... something like the following is what i'm aiming for:

import net.jxta.ext.config.AbstractConfigurator;
import net.jxta.ext.config.Configurator;
import net.jxta.exception.ConfiguratorException;

public class MyConfigurator
extends AbstractConfigurator {
 public PlatformConfig createPlatformConfig(Configurator configurator)
 throws ConfiguratorException {
   configurator.setName("foo");
   configurator.setSecurity("bar", "bop");

   return configurator.getPlatformConfig();
 }
}

but i want to add the following:

• a main method
• instantiate the jxta platform

tim's got a piece of real-world code, as mentioned in his blog, that i'd like to start with, opting to take a small piece per blog and itteratively refactoring the code down the the bare essentials and no more. i suspect the outcome will be significanly application agnostic and perhaps the little thread we spin along the way will be enlightening. i promise, no holds barred with regards to diamonds in the rough, best practices and pitfalls.

tim ... your serve. can you post the code at which point to which i will reference it making subtle tweaks along the way.

MyJXTA :: use it - learn it - do it

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

Secure End-to-End Computing

in my ears: The Crystal Method/Community Service II/SpeedFreak