Difference between revisions of "RMI Interface"
From RifidiWiki
(New page: The Rifidi Edge Server exposes its functionality to clients via Remote Method Invocation (RMI). From the RMI homepage: <blockquote> Java Remote Method Invocation (Java RMI) enables the pr...) |
|||
| Line 6: | Line 6: | ||
RMI stubs are objects that the server creates to handle remote method calls. The Rifidi Edge Server creates three stubs when it starts up, registers them under a given name in the RMI Registry, and registers the objects as services in the OSGi registry. | RMI stubs are objects that the server creates to handle remote method calls. The Rifidi Edge Server creates three stubs when it starts up, registers them under a given name in the RMI Registry, and registers the objects as services in the OSGi registry. | ||
==EdgeServerStub== | ==EdgeServerStub== | ||
| − | This stub handles global Edge server functionality. It is registered in the RMI registry under the name <tt> | + | This stub handles global Edge server functionality, such as saving configurations. It is registered in the RMI registry under the name <tt>EdgeServerStub</tt>. For more information see <link to Javadoc> |
==ReaderStub== | ==ReaderStub== | ||
| + | This stub handles all calls related to Readers, such as creating and deleting readers, changing reader properties, and managing session lifecycle. It is registered in the RMI registry under the name <tt>ReaderStub</tt>. For more information see <link to Javadoc> | ||
==CommandStub== | ==CommandStub== | ||
| + | This stub handles all calls related to commands, such as creating and deleting CommandConfigurations and changing CommandConfiguration properties. It is registered in the RMI registry under the name <tt>CommandStub</tt>. For more information see <link to Javadoc> | ||
=Creating a Client= | =Creating a Client= | ||
==Using native RMI== | ==Using native RMI== | ||
| − | ==Using Rifidi RMI Utils== | + | ==Using Rifidi RMI Utils== |
Revision as of 18:21, 18 May 2009
The Rifidi Edge Server exposes its functionality to clients via Remote Method Invocation (RMI). From the RMI homepage:
Java Remote Method Invocation (Java RMI) enables the programmer to create distributed Java technology-based to Java technology-based applications, in which the methods of remote Java objects can be invoked from other Java virtual machines*, possibly on different hosts. RMI uses object serialization to marshal and unmarshal parameters and does not truncate types, supporting true object-oriented polymorphism.
Contents
Available RMI Stubs
RMI stubs are objects that the server creates to handle remote method calls. The Rifidi Edge Server creates three stubs when it starts up, registers them under a given name in the RMI Registry, and registers the objects as services in the OSGi registry.
EdgeServerStub
This stub handles global Edge server functionality, such as saving configurations. It is registered in the RMI registry under the name EdgeServerStub. For more information see <link to Javadoc>
ReaderStub
This stub handles all calls related to Readers, such as creating and deleting readers, changing reader properties, and managing session lifecycle. It is registered in the RMI registry under the name ReaderStub. For more information see <link to Javadoc>
CommandStub
This stub handles all calls related to commands, such as creating and deleting CommandConfigurations and changing CommandConfiguration properties. It is registered in the RMI registry under the name CommandStub. For more information see <link to Javadoc>
