Does SAND work with JavaSpaces?
Yes. But it doesn’t currently use them. A JavaSpace is a Jini service with semantics similar to a cache: • “write” copies an object into the space • “read” copies an object from the space • “take” copies and removes an object from the space Nothing in the space can be modified. So a JavaSpace provides update atomicity and a consistent reference. This would be one way to implement a cache, or to have several nodes (and/or node instances) working together on a pool of data, or leveraging a pool of processes. For some applications, using a JavaSpace can be a critical part of the overall solution. In a SAND application, components generally react to receiving messages, and reference their own copies of any information they need. Updates will only succeed if they reference the most recent information, with transactional integrity guaranteed by the DataManager. So any data in a SAND application’s JavaSpace must be managed by the application to ensure it is only accessed through the space sem
