Wade Chandler wrote:
*) Jini provides, while not something designed for long term persistence, JavaSpaces, and JEE provides EJB persistence which can be used as short or long term storage.
You might want to reconsider storage via JavaSpace again in terms of loosely coupled communication. While JavaSpaces aren't meant for long-term storage, you can easily enough create a worker that pulls "StorageEntries" from space and writes them to some persistent data store.
You can even have multiple worker processes each dedicated to absorbing different entries and storing them to (perhaps) different locations. Each worker could evaluate whether to store or discard the data on its own criteria without worrying about changing the code that is generating the entries for storage. Workers could even do post-processing of the data before storage, potentially freeing up some computational resources on the system that requests the storage.
I wouldn't suggest that this is a system that you'd want to use every time; just wanted to point out a potential methodology.
James
