Re: River and Backward Compatibility

Greg Trasuk <[email protected]>
Newsgroups gmane.comp.java.sun.jini
Message-ID <1189008887.25074.116.camel@cameron>
Hi Dan:

(I'm not sure if this should be cross-posted back to river-dev.  I'll
leave it to you to post a summary if you think it's appropriate).

I'm not concerned about jar layouts, etc.  I don't want to see any API
or specification changes without big-picture discussion; I'd state this
as "net.jini.**" is currently sacred.  I've always viewed com.sun.jini
as "unsupported" anyway, so change away if that's what you want,
although personally I'd tend to leave it as is and just treat the first
release as an exploration of the release process within the incubator.

Having said that, the log store/PSE issue in Outrigger seems like it
wants to get solved.

Cheers,

Greg.


On Tue, 2007-09-04 at 15:41, Dan Creswell wrote:
> Following Jim's advice, I'm pushing this discussion over to our other lists.
>
> Any thoughts from the community on how much backward compatibility is
> desirable in the first releases from River much appreciated.
>
> On Sep 4, 2007, at 3:47 AM, Dan Creswell wrote:
> > Gregg Wonderly wrote:
> >> Bob Scheifler wrote:
> >>> Gregg Wonderly wrote:
> >>>
> >>>> Perhaps in view that jar layouts may change further, there might be
> >>>> an official directory of deprecated jars so that documentation and
> >>>> discussions can focus on the nature of those jars?
> >>>
> >>> Moving the existing deprecated jars (jini-core.jar, jini-ext.jar,
> >>> sdm-dl.jar, sun-util.jar) could break existing scripts/etc that
> >>> reference them, so if the desire is for AR1 to maintain maximum
> >>> compatibility, it would seem preferable to leave them where they
> >>> are.
> >>
> >> Your call, but my thoughts are that there will already be some
> >> changes
> >> involved in testing and integrating AR1, for many.  So, having to
> >> change
> >> some referred to directory structures, etc, may not be a big impact
> >> overall.
> >
> > What do the rest of the user-base think about this? ^^^
> >
> > How much backward compatibility does everybody expect in this first
> > release?
> >
> > Anybody out there?
>
> Hey Dan-
>
> My guess is that we haven't made enough substantive progress in this
> (River) project yet to attract Jini users to these mailing lists.  We
> certainly
> have some (who seem to be generally lurking), but it will not be
> (IMHO) until
> we get out a release or two before 'users' will start to be very
> vocal on this
> list.
>
> It might be better to ask this at jini/javaspaces-users right now.
>
> My 2c.
>
> -Jim
>
> --------------------------------------------------------------------------
> 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]
--
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]
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.