Re: River and Backward Compatibility
Dan Creswell <[email protected]>
| Newsgroups | gmane.comp.java.sun.jini |
|---|---|
| Message-ID | <[email protected]> |
levmatta wrote: > To people FOR compatibility I have a question. > > How is backwards compatibility going to be achieved if the package name is changing? All backwards compatibility is time-limited otherwise you end up with a pile of cruft that's useless for all. We know this to be true, look at the pain unbounded backward-compatibility causes Intel and Microsoft. So that said: it's likely we'd provide some (limited) form of adapter layer to allow people smooth migration over time (perhaps across a few releases) rather than a brutal cut off. In many cases, that's enough to make people happy to accept the change - build a temporary bridge over the chasm you created...... FWIW: I suspect we'll find that the biggest issues are around com.sun.jini.start and associated scripts and configs that make reference to e.g. com.sun.jini.outrigger.TransientOutriggerImpl > Doesn't that blow the hole thing into pieces: > - compiling does not work (but this could be a simple refactoring step) > - running does not work, because class lookup will fail > > Realizing that in a production environment, one may not be able to recompile everything!!!! > > Chears > > -------------------------------------------------------------------------- > 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] > -------------------------------------------------------------------------- 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]