...
We have chosen to implement this service instead of using JavaSpaces, the tuple-space which has long been part of the Jini Technology package (see http://java.sun.com/developer/products/jini and also http://javaspaces.org), for two the following reasons:
- The API is more limited; we do not require the full generality of JavaSpaces with respect to serializable classes; our service accepts an open-ended (i.e., basically untyped) wrapper object containing a serialized xml blob as payload, corresponding to the
ncsa.tools.common.types.Configuration
object. - There are serious problems with using multicast technologies on NCSA's production resource subnets.
- We do not require the full peer-to-peer capabilities offered by Jini.