I can attest that I am a relative newcomer to JINI. But I certainly
am not a newcomer to networking issues. JINI is a problem in my case
not because of what I don't know but because of what I do know. What
I am saying is that the idea is not to accommodate or to make life
easy for the newcomer but to make JINI make architectural (structural)
sense.
Mike
On Dec 11, 2008, at 5:54 AM, Jools wrote:
2008/12/11 Calum Shaw-Mackay <[EMAIL PROTECTED]>
<snip/>
We all have to go back to where we were when we started and think
about the end to end process that gave us that 'woah that's cool, I
need to look into this technology more' moment and progress that as
one of the core goals, not saying it is the highest priority goal,
but
I get the feeling that we don't care about new people coming to Jini
or about their first-steps experience
And what I was saying earlier was that perhaps we shouldn't. (shock
horror!)
We've been trying to 'make it easier' for as long as I can remember.
Looks
like that approach isn't working out as we expected.
However, there are lots of containers and toolkits out there which
do make
using jini easier. And to be honest that's where the expertise
should be.
The Core concepts for the jini toolkit are there to manage all the
nasty
network stuff, and make the it visible to the user of the toolkit.
No hiding of exceptional situations, forcing you to deal with the
worse case
first. It's all there.
Lets bring the core toolkit up to snuff, make it more manageable for
the
toolkit writers and lets focus on adding functionality to core jini
code.
Let the service container/toolkit writers provide the ease of use,
which
they will.
--Jools
Michael McGrady
Senior Engineer
Topia Technology, Inc.
1.253.720.3365
[EMAIL PROTECTED]
