Package gnu.cajo.invoke

This package is the foundation for completely transparent local/remote inter-VM communication.

See: Description

Interface Summary

Interface	Description
Invoke	The generic inter-component communication interface, and foundation for this paradigm.
RemoteInvoke	The Remote Component Communication Interface, and reason for this package.

Class Summary

Class	Description
Client	This class is used to create a hosting VM to receive a graphical proxy object, from a remote VM.
JClient	This class is used to create a hosting VM to receive a Swing graphical proxy JComponent or and AWT Component, from a remote VM.
NoSecurityManager	This utility class creates a trivial SecurityManager for developing proxy hosting clients.
Remote	This class takes any object, and allows it to be called from remote VMs.

Package gnu.cajo.invoke Description

This package is the foundation for completely transparent local/remote inter-VM communication. It provides a standard interface between local/remote objects, and prevents having to generate unique RMI stubs for every application specific class. (either explicitly or implicitly)

The rationale behind this paradim is to enable seamless dynamic and interchangeable linking between remote and local objects; in order to accomplish advanced functionality. Objects can also be mobile, i.e. moving from one JVM to another, even providing graphical user interfaces to itself, on remote hosts. Objects can even be dynamically linked, with objects from other applications, at runtime. This can support and harness such concepts as scale-free networking, and the emergent phenomena of collective networking.

For the purposes of this paradigm, any object implementing the Invoke interface is considered an Item. If a JVM allows the loading of mobile code, and an item is sent to it, either as an argument, or a return value, that item is referred to as a Proxy, in this architecture.

Also included in the package is the Client and JClient Application/Applet. While strictly non topical to this package, they provide another standard paradigm for creating, hosting, and using graphical proxy items. They could be likened to a successor to X Windows. They are far more capable, being able to perform application specific computation at the client, offloading the server.