Re: Jini vs/and OSGi

Dennis Reedy wrote:
> I personally was not tracking that announcement or move over in OSGi
> land (not sure who from the Jini community was). One can never be  sure
> of the motivation behind this, and from the description o the  link you
> provided I would have to say that the author did not keep up  with the
> Jini technology, the community and the many improvements made.

I never saw any public discussion from OSGI with the Jini community about what
was happening with Jini and how their issues might be or could be addressed.

Loading code into a JVM arbitrarily is a security problem.  Having software in
bundles doesn't present any less risk than loading it off of the network.  It
can be inacurrately signed, improperly assembled and full of bugs, no matter
what anyone would like to guarentee for you.

Thus, the comments they make are not realistically stacked against any arguments
that can provide a real consensus on why OSGI can't have Jini involved with it.

Dennis's comments about micro architecture vs network architecture are the
bigger issue.  People continue to try and make distributed systems programming
simple.  Partial failure guarentees that it can never be simple.

How would you write software if you had to make sure that every instruction your
program caused to be executed worked as it was supposed to?  Distributed systems
have to deal with that kind of issue with every remote interaction.  Luckily,
most distributed systems don't have a remote operation involved in each
instruction.  Jini provides tools to make the needed patterns more easily
composable into a workable system.

Gregg Wonderly

--------------------------------------------------------------------------
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]