Re: RMI query

Well I think just by the sheer number of repsonses recommending JINI I
think I may just have a good look at it tomorrow :p


B. Scott Andersen wrote:

>Documentation?
>
>Jini Specification Jini team (Addison-Wesley)
>http://www.amazon.com/exec/obidos/tg/detail/-/0201616343/
>While it does not cover all the cool new Jini 2.0 features,
>it does give a solid introduction to the general architecture.
>The key concepts have not changed with Jini 2.0 but some of
>the extra capabilities that would help real-world deployments
>have been improved such as pluggable security, dynamic
>configuration of services, pluggable transports using JERI
>(which can be thought of as RMI version 2), etc.
>
>Core Jini (2nd Edition) Keith Edwards (Addison-Wesley)
>http://www.amazon.com/exec/obidos/tg/detail/-/0130894087
>Weighing in at over 1000 pages, this is a complete treatment
>of Jini as it was in version 1.1. Again, there won't be
>anything in there about the new gizmos found in Jini 2.0
>but the discussions for all of the Jini facilities is
>extensive. Edwards did a magnificent job!
>
>Jini Example by Example Keith Edwards, Tom Rodden (Addison-Wesley)
>http://www.amazon.com/exec/obidos/tg/detail/-/0130338583
>Code. Examples. Explainations. This is an excellent place
>to start pulling together that "sample application" once
>you get a feel for the technology.
>
>See also:
>Professional Jini
>http://www.amazon.com/exec/obidos/tg/detail/-/1861003552
>
>A Programmer's Guide to Jini Technology
>http://www.amazon.com/exec/obidos/tg/detail/-/1893115801
>
>Jini and Javaspaces Application Development
>http://www.amazon.com/exec/obidos/tg/detail/-/0672322587
>
>Plus visit http://www.jini.org
>
>Check out the jini-users archives and javaspaces-users
>archives for anything written by John McClain or Brian
>Murphy. (The whole Jini team is fantastic; these two
>fellows just post more explaintions likely to be helpful
>new users.)
>
>As for limiting the packages to those distributed with
>the "standard JVM", well, you're going to deliver _your_
>code, too. You can either write new stuff, or reuse
>stuff that already works, has been tested extensively,
>and proven in the field (the Jini stuff). You'll be
>delivering code outside the standard Java classes.
>It is just a question of how much is new and how much
>is reused. :-)
>
>My 2-cents. Refunds upon request.
>
>--- Scott
>
>B. Scott Andersen
>Verocel, Inc.
>Voice: 978-392-8850
>http://www.verocel.com
>
>-----Original Message-----
>From: Ian Michell [mailto:[email protected]]
>Sent: Tuesday, November 30, 2004 10:58 AM
>To: B. Scott Andersen
>Cc: [email protected]
>Subject: Re: RMI query
>
>I'm not saying I disagree! I would love to play with JINI  from what I
>have read so far it looks like a fantastic base for our code, although
>far too big for what we want.. We are trying to limit the packages that
>we use to those that are distributed with the standard JVM. This means
>that any outside package would have have to be critical.
>
>On top of that I have found next to nothing in the way of documentation
>for JINI...
>
>
>
>B. Scott Andersen wrote:
>
>
>
>>I'd like to second the motion to look at Jini.
>>
>>While it is true that Jini is not bundled "standard"
>>with Java, it is a very close cousin. If you need
>>some facts for your management, try these:
>>
>>* Jini was originally produced by Sun Microsystems
>> and is now organized under a community process--
>> just like Java. jini-users and javaspaces-users
>> are quite active (probably moreso than rmi-users).
>>
>>* The RMI team at Sun is a key contributor to Jini
>> technology. Jini is a logical outgrowth of the
>> RMI model. The RMI team IS part of the Jini team.
>>
>>* Jini has been promenant at the last few JavaONE
>> San Francisco keynote speeches with Orbitz and
>> GE Medical taking center stage. The fellow from
>> Orbitz attributes some of their success to the
>> fact that they are "a Jini shop".
>>
>>Jini technology is possibly a good fit for your
>>solution. Like any technology, there is a learning
>>curve--but it would likely be worth the effort IMHO.
>>
>>My recommendation is thus:
>>Don't let the pointy-haired boss tell
>>you how to code without at least a discussion of
>>the matter. :-)
>>
>>-- Scott
>>
>>B. Scott Andersen
>>Verocel, Inc.
>>Voice: 978-392-8850
>>http://www.verocel.com
>>
>>-----Original Message-----
>>From: Ian Michell [mailto:[email protected]]
>>Sent: Tuesday, November 30, 2004 10:07 AM
>>To: [email protected]
>>Subject: Re: RMI query
>>
>>Have just been reading up on JINI, although I would hate to add another
>>dependancy to our project... JINI is not part of the standard java
>>package and I would have a hard time pushing it forward with my
>>bosses... Is there no simple way to achieve what I am looking for with
>>the standard RMI packages?
>>
>>Regards
>>
>>Ian Michell
>>
>>===========================================================================
>>To unsubscribe, send email to [email protected] and include in the body
>>of the message "signoff RMI-USERS".  For general help, send email to
>>[email protected] and include in the body of the message "help".
>>
>>For a list of frequently asked RMI questions please refer to:
>>http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html
>>
>>To view past RMI-USERS postings, please see:
>>http://archives.java.sun.com/archives/rmi-users.html
>>
>>
>>
>>
>
>
>
>
>
>
>

===========================================================================
To unsubscribe, send email to [email protected] and include in the body
of the message "signoff RMI-USERS".  For general help, send email to
[email protected] and include in the body of the message "help".

For a list of frequently asked RMI questions please refer to:
http://java.sun.com/j2se/1.3/docs/guide/rmi/faq.html

To view past RMI-USERS postings, please see:
http://archives.java.sun.com/archives/rmi-users.html