That is a nice solid article that represents a lot of work. However I don't know if it was a good idea to use JINI 1.2 when JINI 2.0 is now available. Of course, I don't follow JINI news too closely, and JINI 1.2 may be the most commonly used. Personally, I think that JavaSpaces - which use JINI - are really cool. I recently found this discussion of JINI for implementing Grid Computing that folks may find interesting. Bill
As I mentioned in the article, it's a lot easier to get a grip of the Jini 1.2 tools because of the configuration is so simple (none, basically). However, I am aware of exactly what you're after -- why use an already obsolete version -- and will certainly consider using 2.0 in my upcoming journeys in the Jini land. Thanks for the feedback. Dearly appreciated. And yes, JavaSpaces is cool
Wow, thanks for the article. I've only worked with RMI itself and haven't really had time to go reading up on other communication forms. If I understand it correctly, I should be able to use Jini almost like a drop in for straight RMI, correct? I know there will be some setup differences, but Jini is just a more full featured version of the registry right? If this is the case, I'll have to try using it on the next version of the software I am working on. I really like the idea of multi-cast to find the server on the network. Thanks for such a well written article. I've learned something new today. Keep up the good work! Chris oh, I don't mind you writting about 1.2 instead of 2.0. When I'm learning about something new, I have to start somewhere. Especially when the basics of the technology haven't changed much. My best RMI book has been out of print for about 2 years.
Joined: Jan 23, 2002
Thanks for the thanks, Chris
If I understand it correctly, I should be able to use Jini almost like a drop in for straight RMI, correct? I know there will be some setup differences, but Jini is just a more full featured version of the registry right?
Basically yes. It's just that you distribute your "entry point object" to a Jini lookup service(s) instead of a single RMI registry(ies). Of course, you'll only be using a tiny part of Jini's feature set which doesn't provide that much beyond the RMI registry... Jini lookup services let you decouple the service from the implementation -- something you'd otherwise need to code yourself on top of the plain RMI stuff.
My best RMI book has been out of print for about 2 years.
Hmm. I think I know that book
Author and all-around good cowpoke
Joined: Mar 22, 2000
It is certainly worth joining (free) the jini.org site to see articles on JINI projects, news items, etc. JINI (especially 2.0) does look rather overwhelming at first glance, but keep on trucking, there is neat technology there which I think is important to the future of computing. Bill
Joined: Jun 27, 2000
Thanks for the link, Bill. I'll go check that out. A lot of these good sites seem really obvious once you know they exist, but since I'v never looked into the technology, I've never even thought about looking for their home site. Chris
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Journal Article - Service your application with Jini