|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||
See:
Description
| Interface Summary | |
|---|---|
| AbstractConnectionMap.ConnectionMapListener<V> | |
| BasicConnectionTable.ConnectionListener | Used to be notified about connection establishment and teardown. |
| BasicConnectionTable.Receiver | Used for message reception. |
| Cache.ChangeListener | |
| Connection | |
| ConnectionMap<V extends Connection> | |
| LazyRemovalCache.Printable<K,V> | |
| MethodLookup | |
| PartitionedHashMap.HashFunction<K> | |
| ReplCache.ChangeListener | |
| ReplCache.HashFunction<K> | |
| ReplCache.HashFunctionFactory<K> | |
| ReplicatedHashMap.Notification<K,V> | |
| ReplicatedMap<K,V> | |
| ReplicatedTree.ReplicatedTreeListener | |
| RequestHandler | |
| RpcDispatcher.Marshaller | |
| RspCollector | |
| RspFilter | Interface defining when a group request is done. |
| TCPConnectionMap.Receiver | Used for message reception. |
| Class Summary | |
|---|---|
| AbstractConnectionMap<V extends Connection> | |
| BasicConnectionTable | Shared class for TCP connection tables. |
| Cache<K,V> | Simple cache which maintains keys and value. |
| Cache.Value<V> | |
| ConnectionTableNIO | Manages incoming and outgoing TCP connections. |
| ConnectionTableNIO.MyFuture | |
| ConnectionTableNIO.SelectorWriteHandler | |
| ConnectionTableNIO.WriteRequest | |
| GridFile | Subclass of File to iterate through directories and files in a grid |
| GridFile.Metadata | |
| GridFilesystem | Entry point for GridFile and GridInputStream / GridOutputStream |
| GridInputStream | |
| GridOutputStream | |
| GroupRequest<T> | Sends a message to all members of the group and waits for all responses (or timeout). |
| LazyRemovalCache<K,V> | Cache which doesn't remove elements on remove(), removeAll() or retainAll(), but only removes elements when a configurable size limit has been exceeded. |
| MemcachedConnector | Class which listens on a server socket for memcached clients, reads the requests, forwards them to an instance of PartitionedHashMap and sends the response. |
| MemcachedConnector.Request | |
| MessageDispatcher | Provides synchronous and asynchronous message sending with request-response correlation; i.e., matching responses with the original request. |
| MethodCall | A method call is the JGroups representation of a remote method. |
| PartitionedHashMap<K,V> | Hashmap which distributes its keys and values across the cluster. |
| PartitionedHashMap.ConsistentHashFunction<K> | |
| ReplCache<K,V> | Cache which allows for replication factors per data items; the factor determines how many replicas
of a key/value we create across the cluster. See doc/design/ReplCache.txt for details. |
| ReplCache.ConsistentHashFunction<K> | |
| ReplCache.Value<V> | |
| ReplicatedHashMap<K,V> | Implementation of a ConcurrentMap with replication of the contents across a cluster. |
| ReplicatedTree | A tree-like structure that is replicated across several members. |
| ReplicatedTree.Node | |
| Request | Abstract class for a unicast or multicast request |
| RequestCorrelator | Framework to send requests and receive matching responses (matching on request ID). |
| RequestCorrelator.Header | The header for RequestCorrelator messages |
| RequestCorrelator.MultiDestinationHeader | |
| RequestOptions | Class which captures a bunch of options relevant to remote method invocation or message sending |
| RpcDispatcher | This class allows a programmer to invoke remote methods in all (or single) group members and optionally wait for the return value(s). |
| TCPConnectionMap | |
| UnicastRequest<T> | Sends a request to a single target destination |
| Enum Summary | |
|---|---|
| MemcachedConnector.Request.Type | |
| ResponseMode | Enum capturing the various response modes for RPCs |
Provides building blocks that are layered on top of channels. Most of them do not even need a channel, all they need is a class that implements interface Transport (channels do). This enables them to work on any type of group transport that obeys this interface. Building blocks can be used instead of channels whenever a higher-level interface is required. Whereas channels are simple socket-like constructs, building blocks may offer a far more sophisticated interface. In some cases, building blocks offer access to the underlying channel, so that - if the building block at hand does not offer a certain functionality - the channel can be accessed directly.
|
||||||||||
| PREV PACKAGE NEXT PACKAGE | FRAMES NO FRAMES | |||||||||