Z Juhasz wrote:
Greg,
For example, we don't have mechanisms which would allow a
ServiceUI client, to "see" a service in the registrar, and
only after seeing it and its source, signify trust, and then
download code. The original design has always been around
the concept of "you start the VM with the trust asserted" and
then it can only do what you've entrusted it with.
Exactly. Different trust evalutation is essential in the ServiceUI case. We
have had these problems many times. This is a very different mode of
operation from that of the original Jini programmatic clients only view.
Zoltan
Can you tell me more about some of the problems you've experienced,
trying to determine trust using Service UI? Perhaps we can figure
something out?
Service UI is much more flexible than a Jini Service by itself, since
the ServiceUI is really only tied to a JFrame rather than the Service
API which has to be known in advance.
When you think about Service UI, a single UI instance will work on many
services with identical Service API, it really depends on the client
Java platform, as to the Service UI instance chosen. A company will
want to provide their own look and feel. I guess different Service UI
could be akin to skins in media players.
But Service UI also enables the use of anonymous Service API, that is
not known in advance or may not be publicly available.
Any ideas?
Peter.
