|PREV PACKAGE NEXT PACKAGE
|FRAMES NO FRAMES
|A factory to build commands, initializing and injecting dependencies accordingly.
|Commands of this type manipulate data in the cache.
|Commands affected by Flags should carry them over to the remote nodes.
|This is a marker interface to indicate that such commands will never be replicated and hence will not return any valid command IDs.
|The core of the command-based cache framework.
|A type of command that can accept
Visitors, such as
|An abstract implementation of a Visitor that delegates all visit calls to a default handler which can be overridden.
|Specifically used to create un-initialized
ReplicableCommands from a byte stream.
|Command to stop a cache and remove all its contents from both memory and any backing store.
Commands that operate on the cache, either locally or remotely. This package contains the entire command object
model including interfaces and abstract classes. Your starting point is probably
represents a command that can be used in RPC calls.
VisitableCommand, represents commands that can be visited using the visitor pattern.
Most commands that relate to public
Cache API methods tend to be
VisitableCommands, and hence the
importance of this interface.
Visitor interface is capable of visiting
VisitableCommands, and a useful abstract implementation
CommandInterceptor, which allows you to create
interceptors that intercept command invocations adding aspects of behavior to a given invocation.