How does TSpaces relate to Jini?
First, let’s see if we can briefly define the two systems. Jini is a set of components for performing automatic discovery of devices on the local area network (e.g. digital cameras, network storage, or printers), managing those device resources via leasing mechanism, and coordinating them via distributed events and messages (JavaSpaces). TSpaces is a coordination system — a transactional database system that supports asynchronous messaging. The core of TSpaces is often used as a pub/sub system, an event notification system, a heterogeneous platform messaging system, an object database, an XML store, or a platform for hosting transcoders, data extractors or gateways. While there is an overlap in the two systems, they have different purposes. The core of TSpaces is oriented towards coordination, whereas the core of Jini is oriented towards discovery. So, you could think of it this way: Jini is the singles bar for entities/objects/services (where they get introduced) and TSpaces is the c