I can imagine using Javaspaces to help implement the co-ordination part of extreme data manipulation but I wouldn’t imagine using them to hold or transport the data itself unless the chunks of data are small (I wouldn’t use a JavaSpace for passing around huge log files).

Generally, if I advocate the use of a JavaSpace it will be with a specific context and I’ll present some analysis. I appreciate some of the vendors in this vertical like to portray their software as being very broadly applicable in all sorts of “extreme” circumstances and thus it can be confusing.

The above was not intended as a JavaSpaces piece just a line of thinking I’d been pursuing in respect of “do it all” type products, their inherent flexibility problems and how that impacts architecture, design and code.

HTH,

Dan.

are the “javaspaces” products a good fit in those certain circumstances?, especially, in extreme data manipulation applications?.