Package gnu.cajo.utils.extra

A set of optional classes, providing insights on potentially standard ways to extend and use the framework.

See: Description

Class Summary

Class	Description
AsyncMethod	This class is used to asynchronously invoke methods on objects.
AuditorItem	This class is used to transparently pre and post-pend audit functionality to any given object reference.
ClientProxy	This class is used to send server item callbacks to a firewalled client.
DynamicObject	This is a dynamic server object dispatcher.
HashedProxy	This class is used to hash a ZippedProxy.
Implements	This class takes any service object, and allows its methods to be tested for existence, without having to invoke them.
InterceptorItem	This class is used to transparently intercept method invocations on any given object reference.
ItemProxy	This class is used to receive server item callbacks by a firewalled client.
Nice	This class wraps an object, and dynamically alters the priority of the invocation thread at runtime.
Queue	This class is a cajo-based implementation of the message communication paradigm.
Registry	This class runs as a server.
Scheduler	This class is for scheduling the non-preemptive execution of tasks.
Timer	This class supports the timed execution of scheduled tasks.
TransparentItemProxy	This class creates an object, representing a server item.
Wrapper	The base class for wrapping objects, remote references, and proxies for syntactical transparency with the remaining codebase.
Xfile	This class is used to transfer files between Java Virtual Machines.
Zedmobject	This class is used to transfer an object between Virtual Machines as a zipped marshalled object (zedmob).

Package gnu.cajo.utils.extra Description

A set of optional classes, providing insights on potentially standard ways to extend and use the framework. The purpose is purely illustrative, and hopefully useful, but ultimately inessential to making use of the project. Rather they are included here, to minimise the 'learning-curve' assocaited with becoming familarised with the project.

Many of these classes have resulted from discussions in the project fora, concerning common design issues. As with the other project packages, if these classes should be modified, or extended, it will be in a backward compatible fashion.