Uses of Package
org.infinispan.commands
Package
Description
Commands that operate on the cache, either locally or remotely.
Meta-commands that wrap other commands for remote execution.
Contexts contain information of a specific invocation on the cache, such as its origins, scope
(transactional or non-transactional), as well as invocation-specific flags.
This package contains different context implementations, selected dynamically based on the type of invocation.
Classes related to eviction.
Factories are internal components used to create other components based on a cache's
configuration.
Infinispan is designed around a set of interceptors around a data container.
Externalizers for various JDK types that are marshalled using the marshalling framework.
Cache
-specific notifications and eventing.Remote Procedure Call (RPC) interfaces and components used to invoke remote methods on cache instances.
Transports handle the low-level networking, used by the remoting components.
A transport implementation based on JGroups.
General utilities that are not specific to Infinispan, including string parsing helpers, reflection tools and
collections and containers designed to supplement the JDK-provided containers.
Lock and synchronization related classes, tools and utilities.
-
ClassDescriptionA factory to build commands, initializing and injecting dependencies accordingly.A type of command that can accept
Visitor
s, such asDDAsyncInterceptor
. -
ClassDescriptionBase class for those commands that can carry flags.Represents an unique identified for non-transaction write commands.A factory to build commands, initializing and injecting dependencies accordingly.Flags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.The core of the command-based cache framework.Interface to be implemented when the command can define a single segment for its operation.Some of the commands sent over the wire can only be honored by the receiver if the topology of the cluster at delivery time is still 'compatible' with the topology in place at send time (eg.A type of command that can accept
Visitor
s, such asDDAsyncInterceptor
. -
ClassDescriptionCommands of this type manipulate data in the cache.Flags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.The core of the command-based cache framework.Interface to be implemented when the command can define a single segment for its operation.Some of the commands sent over the wire can only be honored by the receiver if the topology of the cluster at delivery time is still 'compatible' with the topology in place at send time (eg.A type of command that can accept
Visitor
s, such asDDAsyncInterceptor
. -
-
-
ClassDescriptionFlags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.A type of command that can accept
Visitor
s, such asDDAsyncInterceptor
. -
ClassDescriptionFlags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.
-
ClassDescriptionFlags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.
-
ClassDescriptionCommands of this type manipulate data in the cache.Flags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.The core of the command-based cache framework.Interface to be implemented when the command can define a single segment for its operation.Some of the commands sent over the wire can only be honored by the receiver if the topology of the cluster at delivery time is still 'compatible' with the topology in place at send time (eg.A type of command that can accept
Visitor
s, such asDDAsyncInterceptor
. -
-
-
ClassDescriptionA factory to build commands, initializing and injecting dependencies accordingly.
-
-
-
ClassDescriptionCommands correspond to specific areas of functionality in the cluster, and can be replicated using the
GlobalInboundInvocationHandler
.The core of the command-based cache framework. -
ClassDescriptionSpecifically used to create un-initialized
ReplicableCommand
s from a byte stream.The core of the command-based cache framework. -
ClassDescriptionFlags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.
-
-
-
ClassDescriptionFlags modify behavior of command such as whether or not to invoke certain commands remotely, check cache store etc.
-
-
-
-
-
-
-
ClassDescriptionA factory to build commands, initializing and injecting dependencies accordingly.
-
ClassDescriptionA factory to build commands, initializing and injecting dependencies accordingly.
-
ClassDescriptionA factory to build commands, initializing and injecting dependencies accordingly.The core of the command-based cache framework.Some of the commands sent over the wire can only be honored by the receiver if the topology of the cluster at delivery time is still 'compatible' with the topology in place at send time (eg.
-
-
ClassDescriptionCommands correspond to specific areas of functionality in the cluster, and can be replicated using the
GlobalInboundInvocationHandler
.The core of the command-based cache framework. -
ClassDescriptionA factory to build commands, initializing and injecting dependencies accordingly.The core of the command-based cache framework.