[Sorry, I intended to start a new thread, but failed miserable for proper email readers]
Dan Creswell wrote:
And that's all fine but: (1) Realize that all your good work elsewhere mightn't get recognized/used if we don't look seriously at the issue. After all, no user community, no interest in all the good stuff Mark has done.
I believe I said it to be important, but with the work up on my sleeves I must make priorities too. Personally I think there is enough good documentation about the concepts of Jini, with regard to the hard stuff I think most people should be shielded of that, or rather unaware, or it is that hard they have the dig the specs anywhere, but this is another topic I guess. But believe me, I won't be a roadblock when others want to go ahead, only when it is decided javadoc is the wrong place for specifications I will foam with rage ;-)
(2) The stuff that you do elsewhere can make it more difficult to get users through the door if it's the wrong choice for them whilst being the right choice for you.
That might be very well the case, but I always have great difficulties valuing that against my own beliefs.
And I'd say let's get ourselves up and running and worry about this issue when we hit it. There's lots of other stuff that needs doing as well.
I've pipelined a few things that will hit this issue, so for me it is imminent. But for me it was a roadmap issue not one thing we should decide upon now. -- Mark
