Managing a Client Cache

You have several options for client cache configuration. Start your client cache using a combination of XML declarations and API calls. Close the client cache when you are done.

Geode clients are processes that send most or all of their data requests and updates to a Geode server system. Clients run as standalone processes, without peers of their own.

Note:
Geode automatically configures the distributed system for your ClientCache as standalone, which means the client has no peers. Do not try to set the gemfire.propertiesmcast-port or locators for a client application or the system will throw an exception.

Note:
Applications that use a client-cache may want to set concurrency-checks-enabled to false for a region in order to see all events for that region. Geode server members can continue using concurrency checks, but they will pass all events to the client cache. This configuration ensures that the client sees all region events, but it does not prevent the client cache region from becoming out-of-sync with the server cache. See Consistency for Region Updates.

If you use multiple server pools, configure the pool name explicitly for each client region. Example: