RendezVous is French for Jini

Jini: Out of the Bottle and Into the Box is the kind of article that make you believe in Jini again. Daniel H. Steinberg makes the open dream of having Jini shipped with every JVM. It would indeed be rather exciting to have Jini on every Java capable device and offer the same services (and more!) as RendezVous. I must admit that Jini is one of the few Java technology that tickles my creativity.

- Dietzen posited that where the current Web is concerned with UI, the next generation of the Web will center around integration.
- SOAP-based web services are being used inappropriately for applications that require only a socket or two.
- It isn’t that Jini or any other technology is right or wrong. You need to understand the fundamental assumptions of that technology and apply it where appropriate.
- We’re buying into the notion that we need all of these WS-* initiatives and can’t imagine that we can send a message “from scratch” with our “easy-bake socket.”
- If you assume Java is present at both ends of the wire, you are mostly set up to take advantage of Jini technology.
- They explained that Jini was all about distributed objects and networked devices, and the assumptions that needed to be made to robustly provide services on an unreliable network. Much of that message got lost.
- Rendezvous is French for Jini
- What we learned in the case of Rendezvous is that having the supporting structure always available leads developers to take advantage of the technology in ways that cannot be anticipated.
- The advantage of supporting Jini at the VM level is, therefore, that you can “assume a network.”
- One of the most appealing aspects of Apple’s Rendezvous technology is the fundamental rejection of the Highlander principle.
- Programmers need to acknowledge and code for potential problems on the network, but the patterns for working with Jini and JavaSpaces are not nearly as complex as the problems with working with EJBs.
- Opportunities abound on the desktop, in the enterprise, and in mobile devices
- There needs to be an ease of use for end users that would require a Jini lookup service be present without requiring any action on their part.