To be specific, SOAP is the "piece of plumbing" and JINI is the "set of blueprints."
His review of what JINI is:
Okay, so let's review:Is peer-to-peer networking an underused tool in service-oriented programming?
In summary, JINI provides you with just enough definition and specification to give you sufficient mechanisms to build a bunch of distributed services. What those services can do, how they are implemented and so on is not defined and the starter kit is nothing more than one example of implementation it is not the only way of doing things and it's not a reference implementation - just ask SUN if you don't believe me.
- JINI is a design approach/philosophy.
- It's based on the concept of services defined as a Java interface with no restriction on function or granularity. The interface might be styled on RPC or it might be styled as a piece of business logic or it might look like a message queue or anything in between.
- Beyond the interface will be a proxy likely written in Java.
- Nothing beyond the proxy need be Java.
- JINI is protocol agnostic - you can use SOAP, RMI, JERI, sockets, JMS or whatever.