Re: River and Backward Compatibility

Greg I was being generic (and vague),
   but I do have some thoughts on "access to the new functionality in this layer". As of new functionality, I can only say I do not like Entry's or command line parameters but I do like generics.

  Ok, so were are doing and adapter layer.
Requirements:
  - Compile against familiar interfaces (familiar scripts, files and their locations)
  - Run on new implementation

Basically I am saying, have a intermediate service implementing old interfaces on top of River.
To access new functionality, or if you will new interfaces, these services can either also implement the new ones or implement access interfaces. 

So, either:

public class A implements Old, New { }

OR:

public interface Access2New {
  public New getNew();
}

public class A implements Old, Access2New { }

That was my thinking,
Thanks.

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]