QCG - Sim IJskes wrote:
Hello,
i've seen a lot of references on the internet to a jxta jeri endpoint
implementation. A lot of people have attempted it, but no-one has
donated it under the ASF license.
I have a jeri-only reggie/joinmanager/jerilookuplocator prototype
running, and believe it is possible to elegantly glue jini to jxta.
Is there an interest in taking river forward into providing:
* a jxta endpoint implementation
* refactoring TCP/UDP (Socket) dependencies into delegates
* providing jxta based remote classloaders
I think that it would be interesting to have this visible as an example of the
intent of JERI's layers. I think that at this point, we have some good ideas of
how to separate the class-loading control out of net.jini.loader into an SPI
which will allow platform specific classloading schemes to be supported. We do
need to make an effort to decide whether this should in fact be something that
is specified as an argument to the InvocationLayerFactory, or somewhere else in
that hierarchy, or completely orthogonal to that mechanism. As I think about
this, I think it should actually be near the ILF because that is the place where
different types of external systems can become accessible to a Jini
client/service. But from other perspectives, one can think that there is also
the case of other platforms wanting to use JERI formulated endpoints, and they
need a mechanism that is completely focused on there mechanism for endpoint
delivery/activation.
Gregg Wonderly
