Re: River and Backward Compatibility

Hi again:

        Thanks for the reply.  Could you answer the question below about the
Entry objects?

Thanks,

Greg.

On Wed, 2007-09-05 at 08:38, levmatta wrote:
> 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
Entry objects are pretty core to Jini's lookup approach, as well as
JavaSpaces.  What is it you don't like about them?

> 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 { }
>

This approach is very "Jini-ish". If you want to use the New interface,
you specify it in your ServiceTemplate when you do your lookup (of
course you know that, but there are beginners on the list). The approach
below is less Jini-ish.

> OR:
>
> public interface Access2New {
>   public New getNew();
> }
>
> public class A implements Old, Access2New { }
>
> That was my thinking,
> Thanks.
--
Greg Trasuk, President
StratusCom Manufacturing Systems Inc. - We use information technology to
solve business problems on your plant floor.
http://stratuscom.com

--------------------------------------------------------------------------
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]