--- Matt Albrecht <[EMAIL PROTECTED]> wrote:
--cut---
> Ok, onto my JOSSystem idea:
> =======================
>
> Jini offers Java applications a unified method of
> discovering all known
> devices (technically, "services") on a network (or
> a stand-alone PC). Not
> only that, but it includes a unified method to
> interact with all discovered
> devices.
>
Note: this is with JINI devices or proxies...
Here (I think) is the problem with your ideas.
Discovery and Join only occures with JINI(TM) enabled
devices and proxies for those devices. I agree we
should make a proxie for all of hardware in JOS but
this is independent of our java written drivers. It
would be interesting; however, to create general
interfaces that can be used in a JINI network that
allows direct access to JOS System drivers from
accross the network(but I digress).
> I say, let's code all our device drivers to that
> standard. But wait -
> doesn't Jini require a network? But at boot time,
> JOS doesn't have a
> network yet, Matt!
>
> The current Jini specification talks about a network
> (and thus RMI) as the
> underlying "bare iron" for a djinn (Jini network).
> However, if I read the
> small print right, using datagram broadcast for
> discovery, and RMI for
> across-the-wire communication, is only the /default/
> implementation. I
> believe that we can still be Jini compliant by
> making a non-network Jini
> network (or is that doublethink?).
>
> If we place the localized Jini lookup service in a
> well-defined location
> (say, the base shared object in JOS, or an parameter
> in the localized
> discovery method), then localized discovery is done
> by calling the local
> lookup service directly, without the need for a
> network. Likewise for
> finding a localized Jini service. Calling a Jini
> service would then be a
> direct Java call, without the need for RMI.
A jini lookup service for the JOS System devices is a
must for JOS Server but if we are going to make a
minimized JOS Client it is more than what is needed.
The JOS Client should export all of its devices to a
jini network.
--cut--
This is great but the problem with jini right now it
that Free Software only has a partial implementation
of RMI let alone jini. It would be great if
development would increase on that. Classpath is
currently the most active in implementation of java
api standards. Next to JOS of course :) (recreating
JAVA OS API).
weo
===
"It's a damn poor mind that can only think of one way to spell
something!"
President Andrew Jackson
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com
_______________________________________________
Kernel maillist - [EMAIL PROTECTED]
http://jos.org/mailman/listinfo/kernel
