Re: class name?

Gregg Wonderly wrote:

> I use the serviceui desktop that I showed at the last JCM.  It's visible
> now out
> on gosie.dev.java.net.  GoSie is a play on the words "go" and "yes".  The
> version that is out there now, is not exactly what I am using currently.  I
> haven't announced it yet, because I am still trying to abstract some
> parts of the security model.

Interesting Gregg, what you might consider over a while is to implement
it on top Seven. I don't know your exact constraints but Seven is not
very large in terms of footprint and will provide you with the ability
to (re)configure all the security requirements [1], things such as
discovery constraints and proxy preparers configured in Seven are also
available through an ordinary Configuration object to the service, and
configuration of Kerberos and SSL has become very imple. As of version
0.1.2 it also provides you with the JAR file cache that survives
restarts of the container for which you also wrote your vhttp protocol
handler.

This is the approach I'm going to take with the Jini Service Browser, if
you are interested you know where to find me. The thing is that if we
want to fully utilize Jini security at some point in time IMHO it is
wise to go with concepts such as proxy preparation et all, regardless of
the way how we/you configure it. A Jini desktop is very valuable to me
but I would expect it to not limit my ability to utilize security. From
what you have told so far security in the ServiceUI desktop seems to
resolve around granting permissions only and not how to configure
constraints or how to perform proxy trust verification [2].

[1] this might require some help from the various Jini utilities as
there are some limitations at those lower layers.

[2] I'm aware this kind of security is not very often utilized, but I'm
still hoping that when River actually starts [frustrated typing]
we can implement Jini across the firewall (in a secure way) so I can
provide support over the Internet for Seven installations in a 'hidden'
data center, or that support people otherwise can monitor their
environment from home or somewhere else. And I bet implementing and
configuring security becomes an issue then. The same applies of course
to any other Jini framework, so this is not something Seven specific and
I don't want to solve this in a Seven proprietary way. It is about time
we are going to cut the restrictions that confines Jini to the LAN ...
who is in for it?
--
Mark

--------------------------------------------------------------------------
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.html
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]