I have been a sad and silent reader of several threads regarding the future of River/Jini/JavaSpaces. I do not wish to add to the heat of the conversation and, unfortunately, I am not confident I can add to the illumination provided.
I am currently reading Practical API Design: Confessions of a Java™ Framework Architect <http://www.apress.com/book/view/9781430209737> by Jaroslav Tulach. (It is a decent read on a difficult topic, I heartily recommend it.) I can understand the desire to maintain backwards compatibility. But I side with the group pointing out adoption has been lower than one might expect for such an interesting and useful resource. I do not attribute the reson to any of the negative adjectives offered as a description of programmers. I am sure it is true for some but not as many as it would take to explain the low adoption. I believe - without being able to prove it - the reason is more likely the api we have does not address the needs (time to learn is one) of the adoptees this technology warrants. (Tulach makes a point regarding java's mail api being optimized, but not for users just interested in reading and sending mail.) I believe - again no proof - well meaning individuals have been trying to raise this issue. I wish they had a better hearing in this forum. Bill
