river-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Firmstone <j...@zeus.net.au>
Subject Towards Internet Jini Services
Date Sat, 25 Sep 2010 08:41:35 GMT
Who's interested in Internet based Jini Services?

River is a Jini platform implementation, Jini's the Standard.

Currently Jini is most suited to private networks, it has advanced tools 
for dealing with security issues like integrity, privacy, identity and 
authorisation, however there are some gaps before the realisation of 
internet based services is possible.

Interesting areas of research:

   1. JERI Endpoint's for Traversing Firewalls (Like Sim's Mekong)
   2. Dealing with Dynamic IP.
   3. Discovery of Registrar's from the Internet. (DNS-SD)
   4. Standards for River's Jini Service Jar Archive Names
      <https://issues.apache.org/jira/browse/RIVER-341> (River-341).
   5. Clients ability to deal with massive lookup result sets, without
      having to download all their jar files. (Similar to Gregg's use of
      delayed unmarshalling)
   6. Automating ClassLoader tree's so that Java, Jini Platform and
      ServiceAPI are loaded into Parent ClassLoader's, while
      applications (containing clients and service implementations) are
      in child ClassLoaders separate from smart proxy's loaded into
      individual child ClassLoader's, to remove the problems developers
      experience with ClassLoading.  All  cooperation communication
      between objects occurs using Service API and Jini and Java
      platform classes.
   7. Distributed Object Registry, for long lived object that move.
   8. Security Improvements for trust, monitoring behaviour, stopping
      and reporting incidents of breaching trust.

There are of course other areas in River requiring attention, like 
concurrency and design improvements, bugs, tests and build improvements.

What are your thoughts?

Peter.


Mime
View raw message