loading...
Connecting Non-Java Devices to a Jini Network
St. Malo, France June 05-June 08
DOI Bookmark: http://doi.ieeecomputersociety.org/10.1109/TOOLS.2000.848750Technology of Object-Oriented Languag ...
 This Article 
 
PDF
HTML
 
 Share 
   
 Bibliographic References 
   
 Add to: 
 
Digg
Furl
Spurl
Blink
Simpy
Google
Del.icio.us
Y!MyWeb
 
 Search 
   
Charles E. McDowell, University of California at Santa Cruz
K. Shankari, University of California at Santa Cruz
Recently, several schemes have been proposed to interconnect extremely small devices in a plug and play manner. One of these is Sun Microsystems' Jini(TM) - which defines a federation of entities, which can communicate with each other. Once a device joins a Jini federation, client programs anywhere on the network can look it up in a central directory and use it by dynamically downloading a proxy, which represents the device.Jini uses the Remote Method Invocation (RMI) mechanism provided by Java at its heart and any entity, which wants to participate in a Jini federation, requires an RMI-enabled Java Virtual Machine. Because embedded devices generally lack the resources to support an RMI-enabled JVM, some other method has to be found to hook them up to a Jini federation. In this paper, we explore the issues involved in connecting non-Java devices to Jini federations by using a Java-based surrogate running on a more powerful machine in the same local network.
Index Terms:
Jini, Java, embedded systems, RMI code download
Citation:
Charles E. McDowell, K. Shankari, "Connecting Non-Java Devices to a Jini Network," tools, pp.45, Technology of Object-Oriented Languages and Systems (TOOLS 33), 2000
Usage of this product signifies your acceptance of the Terms of Use.