Package com.gemstone.gemfire.cache.client

The com.gemstone.gemfire.cache.client package provides APIs used for client connectivity and caching.

See:
Description

Interface Summary

Pool	A pool for connections from a client to a set of GemFire Cache Servers.
PoolFactory	This interface provides for the configuration and creation of instances of Pool.

Class Summary

PoolManager

Manages creation and access to connection pools for clients.

Exception Summary

AllConnectionsInUseException	Indicates that the connection pool is at its maximum size and all connections are in use.
ClientNotReadyException	A ClientNotReadyException indicates a client attempted to invoke the Cache.readyForEvents() method, but failed.
NoAvailableLocatorsException	An exception indicating that there are no active locators available to connect to.
NoAvailableServersException	An exception indicating that there are no active servers available to connect to.
ServerConnectivityException	A generic exception indicating that a failure has happened while communicating with a gemfire server.
ServerOperationException	An exception indicating that a failure has happened on the server while processing an operation that was sent to it by a client.
ServerRefusedConnectionException	A ServerRefusedConnectionException indicates a client attempted to connect to a server, but the handshake was rejected.
SubscriptionNotEnabledException	An exception indicating that client subscriptions are not enabled on this client, but the client is trying to perform an operation that requires a client subscription, such as Region.registerInterest(Object).

Package com.gemstone.gemfire.cache.client Description

The com.gemstone.gemfire.cache.client package provides APIs used for client connectivity and caching.

A client configures the servers it will connect to by creating one or more pools using a factory obtained from the pool manager.

An alternative to these APIs is to use the pool XML element as described in the cache5_7.dtd.

Pools are used by configuring a region to use the pool by setting its pool name using the API or using the pool-name attribute on the region-attributes as described in the cache5_7.dtd.