Can I write/read/take complicated objects using TSpaces, or if it is limited to simple tuples?
A field in a Tuple can be any Serializable object. So in any of the examples that are distributed with TSpaces, you could use a Vector instead of one of the simple String fields. In fact, Example4 uses a user defined object. See the programmer’s guide for a description of Example 4. • Does TSpaces support the concept of lease? The default is that a Tuple will stay in a TupleSpace forever. However you can assign an expiration interval to a Tuple. Sort of like a lease but not exactly. • Is there any kind of offline TSpaces store support? (e.g. if a laptop isn’t connected to the network?) A TSpaces server checkpoints it’s database to stable storage, so it is persistent. A TSpaces client does not have any persistent data itself, so if it gets disconnected from a server, it doesn’t have any of the server state available to it. So, if a client is “offline”, it doesn’t have access to any data. We’re working on Enterprise TSpaces, which includes support for replicated spaces in the server. Onc
