| --- |
| title: Client-Side Configuration |
| --- |
| |
| <!-- |
| Licensed to the Apache Software Foundation (ASF) under one or more |
| contributor license agreements. See the NOTICE file distributed with |
| this work for additional information regarding copyright ownership. |
| The ASF licenses this file to You under the Apache License, Version 2.0 |
| (the "License"); you may not use this file except in compliance with |
| the License. You may obtain a copy of the License at |
| |
| http://www.apache.org/licenses/LICENSE-2.0 |
| |
| Unless required by applicable law or agreed to in writing, software |
| distributed under the License is distributed on an "AS IS" BASIS, |
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. |
| See the License for the specific language governing permissions and |
| limitations under the License. |
| --> |
| |
| All durable messaging configurations are performed on the client. |
| |
| - **[Configuring a Durable Client](configuring-durable-nc.html)** |
| |
| The durable client can be configured in the `geode.properties` file, or in the `CacheFactory::set(name, value)` call. |
| |
| - **[Configuring Durable Interest in Keys](config-durable-interest-keys.html)** |
| |
| When a durable client disconnects, its servers keep queuing messages for selected keys. The client indicates which keys by registering durable interest for those keys. |
| |
| - **[Configuring Durable Client Reconnection](config-durable-reconnect.html)** |
| |
| You can configure the durable client to obtain an approximate count of pending events upon durable client reconnection. Based on the returned number, you can determine whether to proceed and receive the pending events or to close the cache. |
| |
| |
