Bill Venners wrote:
I think JavaSpaces offers an understandable way to distribute processing across multiple cores. Actors do too, but it is a different model and that's OK. There's a lot of buzz these days about actors and Erlang in the context of multi-core CPUs, but no one is talking about JavaSpaces in that same context.
Agreed. I think Javaspaces is a good model for this, and that it might be a good opportunity for River to market itself to those who want to exploit multiple machines/cores.
My points were really just to highlight the differences in the models. I also completely agree with your discussion in a different response in this thread about "chatty versus chunky designs". And I guess I could recharacterise my point by saying that Javaspaces seem better suited to the chunky designs, where as Actors tend to favour chattier models.
Rick.
