Niclas Hedhman wrote:
My argument is that River should have a JavaSpaces implementation that
does not require a network setup, as a stepping stone to lower the
threshold of River adoption. (The "First Shot is Free" comes to mind.)

Niclas, what do you think is the minimum API that would be useful for local space use, and what do you think might be the natural path of code changes that would allow you to move to a remote space?

Gregg Wonderly

Reply via email to