GEODE-1952: removed native client docs, set aside until native client code is 
merged in (see GEODE-1964)


Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo
Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/381d0faa
Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/381d0faa
Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/381d0faa

Branch: refs/heads/develop
Commit: 381d0faaedeba3c8079a03a4da971615d9762da5
Parents: ccc2fbd
Author: Dave Barnes <dbar...@pivotal.io>
Authored: Tue Oct 4 17:15:37 2016 -0700
Committer: Dave Barnes <dbar...@pivotal.io>
Committed: Tue Oct 4 17:15:37 2016 -0700

----------------------------------------------------------------------
 .../about_native_client_users_guide.html.md.erb |  83 -----
 .../cache-init-file/cache-dtd.html.md.erb       | 267 --------------
 .../chapter-overview.html.md.erb                |  21 --
 .../example-cache-file.html.md.erb              |  48 ---
 .../cache-init-file/file-basics.html.md.erb     |  18 -
 .../client-cache/accessing-entries.html.md.erb  |  38 --
 .../adding-entries-to-cache.html.md.erb         |  32 --
 .../application-plugins.html.md.erb             | 262 --------------
 .../client-cache/cache-management.html.md.erb   |  29 --
 .../client-cache/cache-ownership.html.md.erb    |  11 -
 .../client-cache/caches.html.md.erb             |  27 --
 .../client-cache/caching-apis.html.md.erb       |  28 --
 .../client-cache/caching-enabled.html.md.erb    |  27 --
 .../client-cache/chapter-overview.html.md.erb   |  37 --
 .../client-to-server-connection.html.md.erb     |  39 --
 .../client-cache/closing-cache.html.md.erb      |  11 -
 .../concurrency-checks-enabled.html.md.erb      |  18 -
 .../client-cache/concurrency-level.html.md.erb  |  18 -
 .../consistency_checking_in_regions.html.md.erb |  19 -
 .../controlling-cache-size.html.md.erb          |  20 --
 .../create-access-cache.html.md.erb             |  53 ---
 .../declarative-region-creation.html.md.erb     |  38 --
 .../client-cache/disk-policy.html.md.erb        |  34 --
 .../client-cache/entries.html.md.erb            |  20 --
 .../expiration-attributes.html.md.erb           |  65 ----
 .../getting-the-region-size.html.md.erb         |  11 -
 .../client-cache/initial-capacity.html.md.erb   |  15 -
 .../invalidating-cached-entries.html.md.erb     |  16 -
 .../invalidating-region.html.md.erb             |  25 --
 .../client-cache/load-factor.html.md.erb        |  15 -
 .../client-cache/lru-entries-limit.html.md.erb  |  31 --
 .../managing-lifetime-cached-object.html.md.erb |  48 ---
 .../notification-for-operations.html.md.erb     |  16 -
 .../overview-client-cache.html.md.erb           |  24 --
 .../persistence-manager.html.md.erb             | 224 ------------
 .../programmatic-region-creation.html.md.erb    |  24 --
 .../client-cache/region-access.html.md.erb      |  21 --
 .../region-attributes-desc.html.md.erb          |  39 --
 .../client-cache/region-attributes.html.md.erb  |  35 --
 .../client-cache/region-shortcuts.html.md.erb   |  63 ----
 .../client-cache/regions.html.md.erb            |  32 --
 ...registering-interest-for-entries.html.md.erb |  93 -----
 .../requirements-for-distrib.html.md.erb        |  11 -
 .../specify-region-attributes.html.md.erb       |   9 -
 .../client-cache/troubleshooting.html.md.erb    |  41 ---
 .../client-cache/updating-entries.html.md.erb   |  16 -
 .../using-serverkeys-to-retrieve.html.md.erb    |  32 --
 .../using-thread-safety.html.md.erb             |  13 -
 .../common/images/10-Continuous_Querying-1.gif  | Bin 7411 -> 0 bytes
 .../common/images/10-Continuous_Querying-3.gif  | Bin 8611 -> 0 bytes
 .../common/images/6-DotNet_API-1.gif            | Bin 4218 -> 0 bytes
 .../common/images/7-Preserving_Data-2.gif       | Bin 13146 -> 0 bytes
 .../common/images/client-cache-data-flow.gif    | Bin 4422 -> 0 bytes
 .../common/images/client-cache-plugins-run.gif  | Bin 4340 -> 0 bytes
 .../common/images/client-server-arch.gif        | Bin 7198 -> 0 bytes
 .../common/images/data-dep-func-from-client.gif | Bin 10336 -> 0 bytes
 .../common/images/data-dep-func-with-filter.gif | Bin 11062 -> 0 bytes
 .../images/data-indep-func-from-client.gif      | Bin 8105 -> 0 bytes
 .../delta-propagation-in-client-server.gif      | Bin 7115 -> 0 bytes
 .../common/images/delta-propagation.gif         | Bin 8817 -> 0 bytes
 .../common/images/ha-data-dep-func.gif          | Bin 14684 -> 0 bytes
 .../common/images/native-client-overview.gif    | Bin 6421 -> 0 bytes
 .../images/security-client-connections.gif      | Bin 8300 -> 0 bytes
 .../common/images/xact-run-from-client.gif      | Bin 9928 -> 0 bytes
 .../about-connection-pools.html.md.erb          |  20 --
 .../about-server-locators.html.md.erb           |  17 -
 .../client-load-balancing.html.md.erb           |  21 --
 ...iguring-pools-attributes-example.html.md.erb | 156 --------
 .../configuring-pools.html.md.erb               |  25 --
 .../connection-pools.html.md.erb                |  15 -
 ...discovering-locators-dynamically.html.md.erb |  17 -
 .../native-client-pool-api.html.md.erb          |  22 --
 .../running-connection-pool-code.html.md.erb    |  59 ---
 .../subscription-properties.html.md.erb         |  24 --
 .../1-how-cont-query-works.html.md.erb          |  59 ---
 ...2-config-for-continuous-querying.html.md.erb |  15 -
 .../3-native-client-cq-api.html.md.erb          |  41 ---
 .../5-implementing-cq.html.md.erb               |  47 ---
 .../5a-writing-cq.html.md.erb                   |  26 --
 .../5b-writing-cq-listener.html.md.erb          | 280 ---------------
 .../5c-cq-event-object.html.md.erb              |  60 ----
 .../5d-when-error-occurs.html.md.erb            |  17 -
 .../5e-running-cq-code.html.md.erb              |  67 ----
 .../5f-cq-execution-options.html.md.erb         |  13 -
 .../6-managing-cqs.html.md.erb                  |  35 --
 .../continuous-querying.html.md.erb             |  23 --
 .../cpp-caching-api/accessing-entry.html.md.erb |  28 --
 .../add-entry-to-cache.html.md.erb              |  43 ---
 .../cpp-caching-api/cpp-caching-api.html.md.erb |  51 ---
 .../cpp-caching-api/creating-cache.html.md.erb  |  22 --
 .../creating-new-statistics.html.md.erb         |  53 ---
 .../cpp-caching-api/creating-region.html.md.erb |  34 --
 .../cpp-caching-api/data-as-blob.html.md.erb    |  11 -
 .../cpp-caching-api/gfe-cpp-api.html.md.erb     |  61 ----
 .../cpp-caching-api/object-graphs.html.md.erb   |   9 -
 .../pdx_auto_serialization.html.md.erb          | 355 -------------------
 .../pdx_ignore_unread_fields.html.md.erb        |  20 --
 .../pdx_serialization.html.md.erb               |  43 ---
 .../pdx_with_delta_propagation.html.md.erb      |  28 --
 .../pdxserializable_interface.html.md.erb       | 100 ------
 .../performing_ops_with_pdx_object.html.md.erb  |  43 ---
 ...ion_data_requiring_serialization.html.md.erb |  19 -
 .../cpp-caching-api/removing-entry.html.md.erb  |  19 -
 .../serialization_options.html.md.erb           |  65 ----
 .../serialization_overview.html.md.erb          |  31 --
 ...serialization_using_serializable.html.md.erb | 246 -------------
 .../type_interoperability.html.md.erb           |  46 ---
 .../user-defined-objects.html.md.erb            |  31 --
 .../using-custom-class.html.md.erb              |  68 ----
 .../using_enum_type_with_pdx.html.md.erb        | 113 ------
 .../using_pdxinstance.html.md.erb               |  42 ---
 .../using_pdxinstancefactory.html.md.erb        | 117 ------
 .../using_pdxserializer.html.md.erb             | 102 ------
 .../delta-propagation-api.html.md.erb           |  27 --
 .../delta-propagation-examples.html.md.erb      | 335 -----------------
 .../delta-propagation-properties.html.md.erb    |  42 ---
 .../delta-propagation.html.md.erb               |  31 --
 .../how-delta-propagation-works.html.md.erb     |  19 -
 .../implementing-delta-propagation.html.md.erb  |  41 ---
 .../delta-propagation/performance.html.md.erb   |  48 ---
 .../application-callbacks.html.md.erb           |  81 -----
 .../dotnet-caching-api/cache-apis.html.md.erb   |  10 -
 ...p-class-to-dotnet-class-mappings.html.md.erb | 164 ---------
 .../creating-a-cache.html.md.erb                |  33 --
 .../creating-a-region.html.md.erb               |  37 --
 .../csharp-dotnet-api.html.md.erb               |  38 --
 ...csharp-dotnet-naming-conventions.html.md.erb |  15 -
 .../custom-class-igfserializable.html.md.erb    | 136 -------
 .../data-serialization-apis.html.md.erb         |  23 --
 .../dotnet-accessing-an-entry.html.md.erb       |  34 --
 .../dotnet-adding-entry-to-cache.html.md.erb    |  29 --
 .../dotnet-application-domains.html.md.erb      |  16 -
 .../dotnet-caching-api.html.md.erb              |  63 ----
 ...otnet-data-serialization-options.html.md.erb |  64 ----
 .../dotnet-data-serialization.html.md.erb       |  35 --
 .../dotnet-pdx-autoserializer.html.md.erb       |  57 ---
 ...otnet-pdx-serialization-features.html.md.erb |  27 --
 .../dotnet-pdx-serialization.html.md.erb        |  11 -
 .../event-handling-apis.html.md.erb             |  15 -
 .../extending-pdx-autoserializer.html.md.erb    |  59 ---
 .../how-igfserializable-works.html.md.erb       |  19 -
 .../implementing-igfserializable.html.md.erb    | 122 -------
 .../implementing-shared-assembly.html.md.erb    |  21 --
 .../java-to-dotnet-type-mapping.html.md.erb     | 146 --------
 ...mapping-dotnet-domain-type-names.html.md.erb |  25 --
 .../object-lifetimes.html.md.erb                |  37 --
 .../dotnet-caching-api/other-apis.html.md.erb   |  14 -
 .../primary-apis-cache-generic.html.md.erb      |  30 --
 .../private-assembly.html.md.erb                |  39 --
 .../problem-scenarios.html.md.erb               |  24 --
 .../programming-ipdxinstance.html.md.erb        |  45 ---
 .../region-entry-apis.html.md.erb               |  18 -
 .../registering-the-type.html.md.erb            |  27 --
 .../removing-entry.html.md.erb                  |  21 --
 .../resolving-the-error.html.md.erb             |   9 -
 .../serializable-types.html.md.erb              |  20 --
 .../serialize-using-igfserializable.html.md.erb |  23 --
 ...serialize-using-ipdxserializable.html.md.erb | 103 ------
 .../serializing-domain-objects.html.md.erb      |  29 --
 .../simple-csharp-example.html.md.erb           |  43 ---
 ...ubleshooting-dotnet-applications.html.md.erb |  25 --
 .../using-ipdxinstancefactory.html.md.erb       | 111 ------
 .../data-aware-function-execution.html.md.erb   |  11 -
 .../executing-functions.html.md.erb             |  21 --
 .../function-execution.html.md.erb              |  22 --
 .../handling-function-results.html.md.erb       |  34 --
 .../how-functions-execute.html.md.erb           |  60 ----
 .../running-function.html.md.erb                | 122 -------
 .../solutions-use-cases.html.md.erb             |  13 -
 .../chapter_overview.html.md.erb                |  22 --
 .../default_sample_file.html.md.erb             | 104 ------
 .../gfcpp.properties_search_path.html.md.erb    |  11 -
 .../overriding_gfcpp.properties.html.md.erb     |   9 -
 geode-docs/nativeclient/glossary.html.md.erb    | 213 -----------
 .../introduction/developing-linux.html.md.erb   |  86 -----
 .../introduction/developing-solaris.html.md.erb |  44 ---
 .../introduction/developing-windows.html.md.erb |  56 ---
 .../examples-quickstart.html.md.erb             |  15 -
 .../introduction/install-overview.html.md.erb   |   7 -
 .../native-client-intro.html.md.erb             |  25 --
 .../native-client-overview.html.md.erb          |  20 --
 .../introduction/product-examples.html.md.erb   |  19 -
 .../introduction/quickstart.html.md.erb         |  11 -
 .../introduction/runnng-client-apps.html.md.erb |  19 -
 .../app-ops-during-int-reg.html.md.erb          |  17 -
 .../client-side-config.html.md.erb              |  19 -
 .../config-durable-interest-keys.html.md.erb    |  33 --
 .../config-durable-reconnect.html.md.erb        |  42 ---
 .../configuring-durable-nc.html.md.erb          |  38 --
 .../configuring-nc-ha.html.md.erb               |  49 ---
 .../disconnecting-from-server.html.md.erb       |  21 --
 .../preserving-data/disconnection.html.md.erb   |  27 --
 .../durable-client-life-cycle.html.md.erb       |  27 --
 .../durable-client-messaging-req.html.md.erb    |  21 --
 .../durable-client-messaging.html.md.erb        |  31 --
 .../durable-message-replay.html.md.erb          |  27 --
 .../high-availability-client-server.html.md.erb |  20 --
 ...-cache-listeners-durable-clients.html.md.erb |  19 -
 .../initial-operation.html.md.erb               |   9 -
 .../preserving-data/preserving-data.html.md.erb |  21 --
 .../preserving-data/reconnection.html.md.erb    |  32 --
 .../sending-cache-ready-message.html.md.erb     |  19 -
 .../sending-periodic-ack.html.md.erb            |  31 --
 .../using-queue-conflation.html.md.erb          |  25 --
 .../cpp-example.html.md.erb                     |  33 --
 .../csharp-example.html.md.erb                  |  85 -----
 .../native-client-region.html.md.erb            |  29 --
 .../programming-examples.html.md.erb            |  19 -
 .../serialization-cpp.html.md.erb               | 296 ----------------
 .../serialization-csharp.html.md.erb            |  98 -----
 .../serialization-java.html.md.erb              | 210 -----------
 .../serialization-overview.html.md.erb          |  15 -
 .../1-quickintro-overview.html.md.erb           |  19 -
 .../2-quickintro-querycodeexamples.html.md.erb  |  40 ---
 .../3-quickintro-requirements.html.md.erb       |  43 ---
 ...uickintro-exampleportfolioregion.html.md.erb |  60 ----
 ...quickintro-query-portfolioregion.html.md.erb |  97 -----
 ...-quickintro-modify-cachecontents.html.md.erb |  25 --
 .../2-accessingdata.html.md.erb                 |  14 -
 .../21-basic-region-access.html.md.erb          |  31 --
 .../22-drilldown-modify-query-scope.html.md.erb |  29 --
 .../23-attribute-visibility.html.md.erb         |  49 ---
 .../24-nested-query-scope.html.md.erb           |  38 --
 .../25-when-names-cant-resolve.html.md.erb      |   5 -
 .../1-querystring-overview.html.md.erb          |  11 -
 .../93-querystrings/3-from-clause.html.md.erb   |  58 ---
 .../3a-iterator-variables.html.md.erb           |  16 -
 ...b-importing-using-object-classes.html.md.erb |  32 --
 .../3c-predefined-class-types.html.md.erb       |  29 --
 .../3d-specify-object-types.html.md.erb         |  53 ---
 .../93-querystrings/4-where-clause.html.md.erb  |  23 --
 .../93-querystrings/5-joins.html.md.erb         |  15 -
 .../6-select-projection-list.html.md.erb        |  19 -
 ...7-select-statement-query-results.html.md.erb | 113 ------
 .../8-query-language-elements.html.md.erb       |  19 -
 .../8a-method-invocation.html.md.erb            |  18 -
 .../8b-query-lang-literals.html.md.erb          |  19 -
 .../8c-type-conversions.html.md.erb             |  31 --
 .../94-indexes/indexes-overview.html.md.erb     |  31 --
 .../1-remote-query-api-overview.html.md.erb     |  23 --
 .../2-create-manage-queries.html.md.erb         |  46 ---
 .../3-query-result-sets.html.md.erb             |  10 -
 .../2-query-code-examples-resultset.html.md.erb |  68 ----
 .../3-query-code-examples-structset.html.md.erb | 192 ----------
 .../remote-querying/remote-querying.html.md.erb |  27 --
 .../security/LDAPserverauth.html.md.erb         |  27 --
 .../nativeclient/security/PKCS.html.md.erb      |  28 --
 .../security/authentication-levels.html.md.erb  |  21 --
 .../security/authforcacheserver.html.md.erb     |  23 --
 .../security/caveatregionservice.html.md.erb    |  26 --
 .../config-clientauthorization.html.md.erb      |  13 -
 .../createsecureconnregionservice.html.md.erb   |  43 ---
 .../security/encrypted-auth.html.md.erb         |  15 -
 .../handling-serv-auth-errors.html.md.erb       |   7 -
 .../security/limitations.html.md.erb            |   9 -
 .../security/overviewauthentication.html.md.erb |  31 --
 .../overviewclientauthorization.html.md.erb     |  21 --
 .../security/overviewencryptcred.html.md.erb    |  42 ---
 .../security/overviewsecurity.html.md.erb       |  29 --
 .../overviewsslclientserver.html.md.erb         |  13 -
 .../security/postopauthorization.html.md.erb    |  15 -
 .../security/security-systemprops.html.md.erb   |  68 ----
 .../nativeclient/security/ssl-setup.html.md.erb | 122 -------
 .../security/systempropsforauth.html.md.erb     |  68 ----
 .../security/usingoperationcontext.html.md.erb  |  23 --
 .../attribute-def-priority.html.md.erb          |  21 --
 .../attributes-gfcpp.html.md.erb                | 264 --------------
 .../cache-server-config.html.md.erb             |  19 -
 .../chapter-overview.html.md.erb                |  19 -
 .../config-overview.html.md.erb                 |  31 --
 .../define-programmatically.html.md.erb         |  18 -
 .../native-client-config.html.md.erb            |  33 --
 .../chapter_overview.html.md.erb                |  21 --
 .../linux_install.html.md.erb                   |  42 ---
 .../solaris_install.html.md.erb                 |  54 ---
 .../windows_install.html.md.erb                 |  37 --
 .../cache_performance_statistics.html.md.erb    |  30 --
 .../chapter_overview.html.md.erb                |  21 --
 .../continuous_query_statistics.html.md.erb     |  14 -
 .../cq_service_statistics.html.md.erb           |  15 -
 .../delta_statistics.html.md.erb                |  14 -
 .../linux_os_statistics.html.md.erb             |  17 -
 .../operating_system_statistics.html.md.erb     |  19 -
 .../pool_statistics.html.md.erb                 |  30 --
 .../region_statistics.html.md.erb               | 113 ------
 .../sampling_statistics.html.md.erb             |  17 -
 .../solaris_os_statistics.html.md.erb           |  17 -
 .../system_performance_statistics.html.md.erb   |  31 --
 .../windows_os_statistics.html.md.erb           |  26 --
 .../how-native-client-xacts-work.html.md.erb    |  39 --
 .../running-native-client-xact.html.md.erb      |  73 ----
 .../suspend-resume-xacts.html.md.erb            |  17 -
 .../transactions/transactions.html.md.erb       |  21 --
 .../type_mappings/chapter_overview.html.md.erb  |  13 -
 ...p-class-to-dotnet-class-mappings.html.md.erb | 169 ---------
 .../java-to-dotnet-type-mapping.html.md.erb     | 147 --------
 296 files changed, 13023 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/about_native_client_users_guide.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/about_native_client_users_guide.html.md.erb 
b/geode-docs/nativeclient/about_native_client_users_guide.html.md.erb
deleted file mode 100644
index e346f14..0000000
--- a/geode-docs/nativeclient/about_native_client_users_guide.html.md.erb
+++ /dev/null
@@ -1,83 +0,0 @@
----
-title:  Native Client User's Guide
----
-
-This Native Client User's Guide provides step-by-step procedures for 
installation, configuration, and development of native clients.
-
-## <a 
id="concept_95BBEBEF16B2481BA1850C0A5C893607__section_0D0A91D84CA44446A3973F1AE4CD3ABA"
 class="no-quick-link"></a>Intended Audience
-
-This guide is intended for anyone who wants to use a native client, including 
C++ and .NET developers programming their applications to use Geode. This guide 
assumes experience developing with C++ and .NET.
-
--   **[Getting Started with a Native 
Client](../nativeclient/introduction/native-client-intro.html)**
-
-    This section gives you a conceptual overview of the native client. It 
shows you how to install the product, build native client applications on 
various platforms, and run the product examples.
-
--   **[Setting System 
Properties](../nativeclient/setting-properties/chapter-overview.html)**
-
-    *Setting System Properties* describes how to configure Apache Geode native 
clients and cache servers to participate in a distributed system.
-
--   **[Configuring the Native Client 
Cache](../nativeclient/client-cache/chapter-overview.html)**
-
-    *Configuring the Native Client Cache* describes the native client cache 
functionality, initialization file, and APIs. It provides information about 
creating and working with caches, cache regions, and region entries.
-
--   **[Working with the C++ 
API](../nativeclient/cpp-caching-api/cpp-caching-api.html)**
-
-    This sectiondescribes the primary classes, and usage conventions for the 
native client C++ API. It demonstrates how to use the API to create caches and 
perform data serialization.
-
--   **[Working with the .NET 
API](../nativeclient/dotnet-caching-api/dotnet-caching-api.html)**
-
-    This section describes the primary classes, usage conventions, and C++ to 
.NET class mappings of the native client .NET API. It demonstrates how to use 
the API to create caches and perform data serialization.
-
--   **[Preserving Data](../nativeclient/preserving-data/preserving-data.html)**
-
-    A server may preserve the data queued and intended to be sent to a native 
client, such that the data is not discarded if communication between the server 
and native client is disrupted. Preservation prevents message loss, which can 
cause a native client to have inconsistent data. Redundant queues and a high 
availability server implementation may further ensure that queued data is not 
lost.
-
--   **[Security](../nativeclient/security/overviewsecurity.html)**
-
-    *Security* describes how to implement the security framework for the Geode 
native client, including authentication, authorization, ecryption, and SSL 
client/server communication.
-
--   **[Remote Querying](../nativeclient/remote-querying/remote-querying.html)**
-
-    *Remote Querying* documents remote querying from the native client to the 
Geode cache server. Using examples and procedures, it describes how to use the 
APIs to run queries against cached data; work with query strings in the native 
client; create and manage queries; and create indexes.
-
--   **[Continuous 
Querying](../nativeclient/continuous-querying/continuous-querying.html)**
-
-    *Continuous Querying* describes how to implement continuous querying in 
the Apache Geode native client so that C++ and C\# .NET clients can run queries 
against events in the Geode cache server region. It also describes main 
features and the native client CQ API.
-
--   **[Using Connection 
Pools](../nativeclient/connection-pools/connection-pools.html)**
-
-    *Using Connection Pools* describes how connection pools achieve load 
balancing for the client and describes how to configure connection pools as 
server locators or as a list of servers.
-
--   **[Transactions](../nativeclient/transactions/transactions.html)**
-
-    *Transactions* describes how transactions work on the client side. It 
provides examples for running, suspending, and resuming transactions.
-
--   **[Function 
Execution](../nativeclient/function-execution/function-execution.html)**
-
-    *Function Execution* describes how you can execute application functions 
to achieve linear scalability. It explains how function execution works and 
lists specific use cases.
-
--   **[Delta 
Propagation](../nativeclient/delta-propagation/delta-propagation.html)**
-
-    *Delta Propagation* describes how deltas (updates to data) are propagated 
and how to implement delta propagation. It also analyzes performance 
limitations.
-
--   **[Programming 
Examples](../nativeclient/programming-examples/programming-examples.html)**
-
-    This chapter provides a set of programming examples to help you understand 
the Geode native client API.
-
--   **[Interoperability of Language Classes and 
Types](../nativeclient/type_mappings/chapter_overview.html)**
-
-    *Interoperability of Language Classes and Types* provides a table that 
maps C++ class methods to corresponding .NET class methods and a table that 
maps Java types to .NET types.
-
--   **[System 
Statistics](../nativeclient/system-statistics/chapter_overview.html)**
-
-    *System Statistics* provides information on the installation and includes 
standard statistics for caching and distribution activities.
-
--   **[Installing the SQLite Persistence 
Manager](../nativeclient/sqlite-persistence/chapter_overview.html)**
-
-    *Installing the SQLite Persistence Manager* describes how to download, 
build and install the SQLite database libraries for use with disk overflow.
-
--   **[Glossary](../nativeclient/glossary.html)**
-
-    This glossary defines terms used in the documentation.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/cache-init-file/cache-dtd.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/cache-init-file/cache-dtd.html.md.erb 
b/geode-docs/nativeclient/cache-init-file/cache-dtd.html.md.erb
deleted file mode 100644
index edf11ba..0000000
--- a/geode-docs/nativeclient/cache-init-file/cache-dtd.html.md.erb
+++ /dev/null
@@ -1,267 +0,0 @@
----
-title:  Native Client Cache XML DTD
----
-
-The contents of the cache initialization file must conform to the data type 
definitions in `gfcpp-cache8000.dtd`.
-
-The `gfcpp-cache8000.dtd` file is in the `productDir/dtd` directory of your 
native client installation.
-
-The following example presents the file `gfcpp-cache8000.dtd`, which defines 
the XML used by the native client for declarative caching. The DTD file 
identifies the valid element tags that may be present in your XML file, the 
attributes that correspond to each element, and the valid values for the 
elements and attributes.
-
-``` pre
-<?xml version="1.0" encoding="UTF-8"?>
-
-<!--
-
-This is the XML DTD for the GemFire Native Client declarative caching XML 
file.  
-
-The contents of a declarative XML file correspond to APIs found in the
-Gemfire Native Client product, more specifically in the
-Cache.hpp and Region.hpp files in the product include directory
-
-A declarative caching XML file is used to populate a Cache
-when it is created.
-
--->
-
-
-<!--
-The "client-cache" element is the root element of the declarative cache file.
-This element configures a GemFire Native Client Cache and describes the 
-root regions it contains, if any.
--->
-
-<!ELEMENT client-cache (pool*, root-region*, region*, pdx?)>
-<!ATTLIST client-cache
-  endpoints CDATA #IMPLIED
-  redundancy-level CDATA #IMPLIED
->
-
-<!--
-A "locator" element specifies the host and port that a server locator is 
listening on
--->
-<!ELEMENT locator EMPTY>
-<!ATTLIST locator
-  host  CDATA #REQUIRED
-  port  CDATA #REQUIRED
->
-
-<!--
-A "server" element specifies the host and port that a cache server is 
listening on
--->
-<!ELEMENT server EMPTY>
-<!ATTLIST server
-  host  CDATA #REQUIRED
-  port  CDATA #REQUIRED
->
-
-<!-- A "pdx" element specifies the properties related to pdx types -->
-<!ELEMENT pdx EMPTY>
-<!ATTLIST 
-  ignore-unread-fields  (false | true) #IMPLIED
-  read-serialized (false | true) #IMPLIED
-  >
-
-<!--
-A "pool" element specifies a client-server connection pool.
--->
-<!ELEMENT pool (locator+|server+)>
-<!ATTLIST pool
-  free-connection-timeout        CDATA #IMPLIED
-  load-conditioning-interval     CDATA #IMPLIED
-  min-connections                CDATA #IMPLIED
-  max-connections                CDATA #IMPLIED
-  retry-attempts                 CDATA #IMPLIED
-  idle-timeout                   CDATA #IMPLIED
-  ping-interval                  CDATA #IMPLIED
-  name                           CDATA #REQUIRED
-  read-timeout                   CDATA #IMPLIED
-  server-group                   CDATA #IMPLIED
-  socket-buffer-size             CDATA #IMPLIED
-  subscription-enabled                  (false | true) #IMPLIED
-  subscription-message-tracking-timeout CDATA #IMPLIED
-  subscription-ack-interval             CDATA #IMPLIED
-  subscription-redundancy        CDATA #IMPLIED
-  statistic-interval             CDATA #IMPLIED
-  pr-single-hop-enabled          (true | false) #IMPLIED
-  thread-local-connections       (false | true) #IMPLIED
-  multiuser-authentication          (false | true) #IMPLIED
->
-
-<!--
-A root-region" element describes a root region whose entries and
-subregions will be stored in memory.
-Note that the "name" attribute specifies the simple name of the region;
-it cannot contain a "/".
--->
-
-<!ELEMENT root-region (region-attributes?, region*)>
-<!ATTLIST root-region
-  name CDATA #REQUIRED
->
-
-
-<!--
-A "region" element describes a region (and its entries) in GemFire
-Native Client cache. Note that the "name" attribute specifies the simple
-name of the region; it cannot contain a "/".
--->
-
-<!ELEMENT region (region-attributes?, region*)>
-<!ATTLIST region
-  name CDATA #REQUIRED
-  refid CDATA #IMPLIED
->
-
-
-
-<!--
-A "region-attributes" element describes the attributes of a region to
-be created. For more details see the RegionFactory header in the
-product include directory
--->
-
-<!ELEMENT region-attributes ((region-time-to-live |
-  region-idle-time | entry-time-to-live | entry-idle-time |
-  partition-resolver |
-  cache-loader | cache-listener | cache-writer | persistence-manager)*)>
-<!ATTLIST region-attributes
-  caching-enabled (true | TRUE | false | FALSE) #IMPLIED
-  cloning-enabled (true | TRUE | false | FALSE) #IMPLIED
-  scope (local | distributed-no-ack | distributed-ack ) #IMPLIED
-  initial-capacity CDATA #IMPLIED
-  load-factor CDATA #IMPLIED
-  concurrency-level CDATA #IMPLIED
-  lru-entries-limit CDATA #IMPLIED
-  disk-policy (none | overflows | persist ) #IMPLIED
-  endpoints CDATA #IMPLIED
-  client-notification (true | TRUE | false | FALSE) #IMPLIED
-  pool-name CDATA #IMPLIED
-  concurrency-checks-enabled (true | TRUE | false | FALSE) #IMPLIED
-  id CDATA #IMPLIED
-  refid CDATA #IMPLIED
->
-
-
-
-
-
-
-<!--
-A "region-time-to-live" element specifies a Region's time to live
--->
-
-<!ELEMENT region-time-to-live (expiration-attributes)>
-
-
-
-<!--
-A "region-idle-time" element specifies a Region's idle time
--->
-
-<!ELEMENT region-idle-time (expiration-attributes)>
-
-
-
-<!--
-A "entry-time-to-live" element specifies a Region's entries' time to
-live
--->
-
-<!ELEMENT entry-time-to-live (expiration-attributes)>
-
-
-
-<!--
-A "entry-idle-time" element specifies a Region's entries' idle time
--->
-
-<!ELEMENT entry-idle-time (expiration-attributes)>
-
-
-<!--
-A "properties" element specifies a persistence properties 
--->
-
-<!ELEMENT properties (property*)>
-
-<!-- 
-An "expiration-attributes" element describes expiration 
--->
-
-<!ELEMENT expiration-attributes EMPTY>
-<!ATTLIST expiration-attributes
-  timeout CDATA #REQUIRED
-  action (invalidate | destroy | local-invalidate | local-destroy) #IMPLIED
->
-
-
-
-<!--
-A "cache-loader" element describes a region's CacheLoader
--->
-
-<!ELEMENT cache-loader  EMPTY >
-<!ATTLIST cache-loader 
- library-name CDATA #IMPLIED
- library-function-name CDATA #REQUIRED
->
-
-
-
-<!--
-A "cache-listener" element describes a region's CacheListener
--->
-
-<!ELEMENT cache-listener EMPTY>
-<!ATTLIST cache-listener 
- library-name CDATA #IMPLIED
- library-function-name CDATA #REQUIRED
->
-
-
-
-<!--
-A "cache-writer" element describes a region's CacheListener
--->
-
-<!ELEMENT cache-writer EMPTY>
-<!ATTLIST cache-writer 
- library-name CDATA #IMPLIED
- library-function-name CDATA #REQUIRED
->
-
-<!--
-A "partition-resolver" element describes a region's PartitionResolver
--->
-
-<!ELEMENT partition-resolver EMPTY>
-<!ATTLIST partition-resolver 
- library-name CDATA #IMPLIED
- library-function-name CDATA #REQUIRED
->
-
-<!--
-A "persistence-manager" element describes a region's persistence feature
--->
-
-<!ELEMENT persistence-manager (properties)>
-<!ATTLIST persistence-manager 
- library-name CDATA #IMPLIED
- library-function-name CDATA #REQUIRED
->
-
-
-
-<!--
-A "property" element describes a persistence property
--->
-
-<!ELEMENT property EMPTY>
-<!ATTLIST property 
- name CDATA #REQUIRED
- value CDATA #REQUIRED
->
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/cache-init-file/chapter-overview.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/cache-init-file/chapter-overview.html.md.erb 
b/geode-docs/nativeclient/cache-init-file/chapter-overview.html.md.erb
deleted file mode 100644
index 5c55033..0000000
--- a/geode-docs/nativeclient/cache-init-file/chapter-overview.html.md.erb
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title:  Cache Initialization File (cache.xml)
----
-
-To ease the task of managing the structure of the cache, you can define the 
default Geode cache structure in an XML-based initialization file.
-
-This section describes the file format of the `cache.xml` file and discusses 
its contents.
-
--   **[Cache Initialization File 
Basics](../../nativeclient/cache-init-file/file-basics.html)**
-
-    The contents of the cache initialization file are used to populate or 
update a cache.
-
--   **[Example cache.xml 
File](../../nativeclient/cache-init-file/example-cache-file.html)**
-
-    An example `cache.xml` file shows cache and region initialization for a 
client, presenting a subset of the possible data configurations.
-
--   **[Native Client Cache XML 
DTD](../../nativeclient/cache-init-file/cache-dtd.html)**
-
-    The contents of the cache initialization file must conform to the data 
type definitions in `gfcpp-cache8000.dtd`.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/cache-init-file/example-cache-file.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/cache-init-file/example-cache-file.html.md.erb 
b/geode-docs/nativeclient/cache-init-file/example-cache-file.html.md.erb
deleted file mode 100644
index 2ad56b0..0000000
--- a/geode-docs/nativeclient/cache-init-file/example-cache-file.html.md.erb
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title:  Example cache.xml File
----
-
-An example `cache.xml` file shows cache and region initialization for a 
client, presenting a subset of the possible data configurations.
-
-For detailed information about cache and region configuration, including the 
default attribute settings, see [The Native Client 
Cache](../client-cache/chapter-overview.html#native-client-cache). Also see the 
online API documentation for `Cache` and `RegionAttributes`.
-
-For information a cache with server pool, see [Using Connection 
Pools](../connection-pools/connection-pools.html#using-connection-pools). The 
example below shows a `cache.xml` file that creates two regions.
-
--   Region `region1` is defined with a full set of region attributes and 
application plug-ins. The region's entries have `RegionTimeToLive` and 
`RegionIdleTimeout` expiration attributes set ([Expiration 
Attributes](../client-cache/expiration-attributes.html#expiration-attributes)).
--   Region `region2` uses mostly default values.
-
-``` pre
-<?xml version="1.0" encoding="UTF-8"?>
-<!DOCTYPE cache PUBLIC
-    "-//Example Systems, Inc.//Example Declarative Caching 8.0//EN"
-    "http://www.example.com/dtd/gfcpp-cache8000.dtd";>
-<!-- Sample cache.xml file -->
-<!-- Example Declarative Cache Initialization with cache.xml -->
-<cache>
-    <pool name="examplePool" subscription-enabled="true">
-        <server host="localhost" port="24680" />
-    </pool>
-    <region name="root1" refid="CACHING_PROXY">
-        <region-attributes pool-name="examplePool"
-            initial-capacity="25"
-            load-factor="0.32"
-            concurrency-level="10"
-            lru-entries-limit="35">
-            <region-idle-time>
-                <expiration-attributes timeout="20" action="destroy"/>
-            </region-idle-time>
-            <entry-idle-time>
-                <expiration-attributes timeout="10" action="invalidate"/>
-            </entry-idle-time>
-            <region-time-to-live>
-                <expiration-attributes timeout="5" action="local-destroy"/>
-            </region-time-to-live>
-            <entry-time-to-live>
-                <expiration-attributes timeout="10" action="local-invalidate"/>
-            </entry-time-to-live>
-        </region-attributes>
-    </region>
-</cache>
-```
-
-For details about the individual region attributes, see [Region 
Attributes](../client-cache/region-attributes.html#region-attributes).

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/cache-init-file/file-basics.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/cache-init-file/file-basics.html.md.erb 
b/geode-docs/nativeclient/cache-init-file/file-basics.html.md.erb
deleted file mode 100644
index ca6fcca..0000000
--- a/geode-docs/nativeclient/cache-init-file/file-basics.html.md.erb
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title:  Cache Initialization File Basics
----
-
-The contents of the cache initialization file are used to populate or update a 
cache.
-
-This occurs when a cache server starts up, when a client application 
explicitly creates its cache, or when a client explicitly loads a new structure 
into an existing cache.
-
-The initialization file can have any name, but is generally referred to as 
`cache.xml`. Both client applications and cache servers can use an optional 
`cache.xml` file to ease the initialization process.
-
-## <a id="file-basics__section_E54BF7911C224016B822768B537FA464" 
class="no-quick-link"></a>File Contents
-
-The contents of a declarative XML file correspond to APIs declared in the 
`Cache.hpp` and `Region.hpp` header files. The cache initialization file allows 
you to accomplish declaratively many of the cache management activities that 
you can program through the API.
-
--   The contents of the cache initialization file must conform to the XML 
definition in `productDir/dtd/gfcpp-cache8000.dtd` (see [Native Client Cache 
XML DTD](cache-dtd.html#cache-dtd)).
--   The name of the declarative XML file is specified when establishing a 
connection to the distributed system. You can define it by setting the 
`cache-xml-file` configuration attribute in the `gfcpp.properties` file for the 
native client. For details about the `gfcpp.properties` file, see [Setting 
System and Cache 
Properties](../setting-properties/chapter-overview.html#system_and_cache_properties).
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/accessing-entries.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/accessing-entries.html.md.erb 
b/geode-docs/nativeclient/client-cache/accessing-entries.html.md.erb
deleted file mode 100644
index 6506e54..0000000
--- a/geode-docs/nativeclient/client-cache/accessing-entries.html.md.erb
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title:  Accessing Entries
----
-
-<a id="accessing-entries__section_310C0BE952BC489C9E97811DAE8736E4"></a>
-Use the API to retrieve the entry key, entry value, and the `RegionEntry` 
object itself. A variety of functions provide information for individual 
entries and for the set of all entries resident in the region. The online API 
documentation lists all available access functions.
-
-A region's entry keys and `RegionEntry` objects are directly available from 
the local cache. Applications can directly access the local cache's stored 
entry value through the `RegionEntry::getValue` function. The `getValue` 
function either returns the value if a valid value is present in the local 
cache, or `NULL` if the value is not valid locally. This function does no data 
loading, nor does it look elsewhere in the distributed system for a valid value.
-
-**Note:** Direct access through `RegionEntry::getValue` does not reset an 
entry's timestamp for LRU expiration. See [Specifying Expiration 
Attributes](expiration-attributes.html#expiration-attributes) for more 
information about LRU expiration.
-
-In comparison, the standard `Region::get` functions consider all caches and 
all applicable loaders in the distributed system in an attempt to return a 
valid entry value to the calling application. The primary attribute setting 
affecting entry retrieval is `CacheLoader`. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).
-
-The standard `Region::get` functions may implement a number of operations in 
order to retrieve a valid entry value. The operations used depend on the 
region's attribute settings and on the state of the entry itself. By default, 
the client retrieves entry values through calls to the `get` function. The 
client can override this behavior for any region by defining a cache loader for 
the region.
-
-The following sections discuss the `get` function and special considerations 
for entry retrieval.
-
-## <a id="accessing-entries__section_AD6AFD842C144C128FA1C7F0B9283372" 
class="no-quick-link"></a>Entry Retrieval
-
-You retrieve entry values with the `Region::get` function.
-
-When an entry value is requested from a region, it is either retrieved from 
the cache server or fetched by the region's locally-defined cache loader in 
this sequence:
-
-1.  local cache search
-2.  server cache
-3.  local load (For distributed regions, the local load is fetched before 
remote cache values)
-
-## <a id="accessing-entries__section_82B624FE364F4034AF010D20A8D0DF68" 
class="no-quick-link"></a>How the get Operation Affects the Local Entry Value
-
-If a `get` operation retrieves an entry value from outside the local cache 
through a local load, it automatically `put`s the value into the cache for 
future reference.
-
-Note that these load operations do not invoke a cache writer. Because the 
loader and writer operate against the same data source, you do not need to 
perform a cache write for entries that were just fetched from that data source. 
For descriptions of these processes, see [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).
-
-**Note:** Access through a `get` operation resets an entry's timestamp for LRU 
expiration.
-
-## <a id="accessing-entries__section_F636614605C84513B2B7F4A674FD6E38" 
class="no-quick-link"></a>Getting Multiple Entries Using getAll
-
-You can use the `getAll` Region API to get all values for an array of keys 
from the local cache or cache server. Under [Bulk Put Operations Using 
putAll](../cpp-caching-api/add-entry-to-cache.html#concept_26D4E6C6BC6F4AB8884E33119999656D__section_748916759F0246619CD27E7456DCA365)
 for more information.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/adding-entries-to-cache.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/adding-entries-to-cache.html.md.erb 
b/geode-docs/nativeclient/client-cache/adding-entries-to-cache.html.md.erb
deleted file mode 100644
index 6b7aa78..0000000
--- a/geode-docs/nativeclient/client-cache/adding-entries-to-cache.html.md.erb
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title:  Adding Entries to the Cache
----
-
-<a id="adding-entries-to-cache__section_57CE90DC5C694CB79F05C943DE6F5E4B"></a>
-A region is populated with cached entries in several ways:
-
--   Explicitly, when an application executes a `create` or a `put` operation 
for a single entry or for multiple entries that do not already exist in the 
cache.
--   Implicitly, when a client does a get on a single entry or on multiple 
entries that do not already exist in the cache. In this case, the entry is 
retrieved from a remote cache or through a cache loader. Under [Specifying 
Application Plug-In Attributes](application-plugins.html#application-plugins), 
see the portion on a cache loader. A client can also use `getAll` to populate a 
region with all values for an array of keys. See [Accessing 
Entries](accessing-entries.html#accessing-entries).
--   Automatically, when entries are created in remote caches.
-
-If any cache writer is available in the distributed region, it is called 
before the entry is created and it can abort the creation process.
-
-**Note:**
-For more information on how to create entries, see [Working with the C++ 
API](../cpp-caching-api/cpp-caching-api.html#concept_CEC658A999414AC3A494578C214BF64E),
 [Working with the .NET 
API](../dotnet-caching-api/dotnet-caching-api.html#concept_FC6776DCE6ED48B887A6137761104AA4),
 and the native client API reference.
-
-## <a id="adding-entries-to-cache__section_873FFF2CAC804B8E9676AB8098CF2434" 
class="no-quick-link"></a>Adding Entries to the Local Cache
-
-If just the local cache is to be populated, you can either `create` an entry 
using the `localCreate` Region API, or `put` an entry using `localPut`. See the 
C++ and .NET online API documentation for details about `localCreate` and 
`localPut`.
-
-`DateTime` objects must be stored in the cache in UTC, so that times 
correspond between client and server. If you use a date with a different time 
zone, convert it when storing into and retrieving from the cache. This example 
converts a local time to UTC for a put operation:
-
-``` pre
-DateTime t1( 2009, 8, 13, 4, 11, 0, DateTimeKind.Local);
-region0.Put( 1, t1.ToUniversalTime() );
-```
-
-## <a id="adding-entries-to-cache__section_7CFEB263E2FE4775A3C9A29351A33911" 
class="no-quick-link"></a>Adding Multiple Entries Using PutAll
-
-If you need to add many cache entries to a region at one time, you can improve 
cache performance by using the `putAll` function to add them in a single 
distributed operation. Multiple key/value pairs are stored in a hashmap, then 
the hashmap contents are processed on the server as either new entries, 
updates, or invalidates for existing entries.
-
-Under [Adding an Entry to the 
Cache](../cpp-caching-api/add-entry-to-cache.html#concept_26D4E6C6BC6F4AB8884E33119999656D)
 see "Bulk Put Operations Using putAll" for more information about the `putAll` 
API. Additional details are available in the online API documentation for 
`Region::putAll` (C++), or `Region.PutAll` (.NET).

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb 
b/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb
deleted file mode 100644
index 8d23295..0000000
--- a/geode-docs/nativeclient/client-cache/application-plugins.html.md.erb
+++ /dev/null
@@ -1,262 +0,0 @@
----
-title:  Specifying Application Plug-In Attributes
----
-
-<a id="application-plugins__section_E81DB00AE0784BA2819DB3683C257647"></a>
-The plug-in attributes allow you to customize client region behavior for 
loading, updating, deleting, and overflowing region data and for accessing data 
in server partitioned regions. All client plug-ins are available through the 
C++ and .NET API.
-
-Application plug-ins for cache regions in clients can be declared either 
programmatically or in the `cache.xml` file.
-
-
-<a id="application-plugins__fig_630074710E134805A96B50AA5373866F"></a>
-<span class="figtitleprefix">Figure: </span>Where Application Plug-Ins Run
-
-<img src="../common/images/client-cache-plugins-run.gif" alt="Where 
Application Plug-Ins Run" 
id="application-plugins__image_23F82DD7DCD543239F3A75F112282C46" class="image" 
/>
-
-## <a id="application-plugins__section_8FEB62EEC7A042E0A85E0FEDC9F71597" 
class="no-quick-link"></a>Overview of Application Plug-ins
-
-The API provides the framework for application plug-ins with callback 
functions for the appropriate events. Your classes and functions can customize 
these for your application's needs. When creating a region, specify these as 
part of the region's attributes settings. For regions already in the cache, you 
can specify new `CacheLoader`, `CacheWriter`, and `CacheListener` using the 
region's `AttributesMutator`. The `PartitionResolver` is not mutable.
-
--   `CacheLoader`: A data loader called when an entry get operation fails to 
find a value for a given key. A cache loader is generally used to retrieve data 
from an outside source such as a database, but it may perform any operation 
defined by the user. Loaders are invoked as part of the distributed loading 
activities for entry retrieval, described in [Entry 
Retrieval](accessing-entries.html#accessing-entries__section_AD6AFD842C144C128FA1C7F0B9283372).
--   `CacheWriter`: A synchronous event listener that receives callbacks before 
region events occur and has the ability to abort the operations. Writers are 
generally used to keep a back-end data source synchronized with the cache.
--   `CacheListener`: An asynchronous event listener for region events in the 
local cache.
--   `PartitionResolver`: Used for single-hop access to partitioned region 
entries on the server side. This resolver implementation must match that of the 
`PartitionResolver` on the server side.
-
-The following XML declaration specifies a cache loader for a region when the 
region is created.
-
-``` pre
-<region-attributes>
-    <cache-loader library-name="appl-lib"
-        library-function-name ="createCacheLoader">
-    </cache-loader>
-</region-attributes>
-```
-
-The rest of this section gives more detailed descriptions of these application 
plug-ins, followed by special considerations for plug-ins in distributed 
regions and some guidelines for writing callbacks.
-
-## <a id="application-plugins__section_FD3057C0416840BAB76850E115F48B5C" 
class="no-quick-link"></a>CacheLoader
-
-A cache loader is an application plug-in used to load data into the region. 
When an entry is requested that is unavailable in the region, a cache loader 
may be called upon to load it. Generally, you use a cache loader to retrieve 
the data from a database or another source outside the distributed system, but 
it may perform any operation defined by the user.
-
-The `CacheLoader` interface provides one function, `load`, for customizing 
region entry loading. A distributed region may have cache loaders defined in 
any or all caches where the region is defined. When loading an entry value, a 
locally defined cache loader is always used before a remote loader. In 
distributed regions, loaders are available for remote entry retrieval.
-
-## <a id="application-plugins__section_1754F575011742A59149FD280CEA0F16" 
class="no-quick-link"></a>CacheWriter
-
-A cache writer is an application plug-in that synchronously handles changes to 
a region's contents. It is generally used to keep back-end data sources 
synchronized with a cache region. A cache writer has callback functions to 
handle region destruction and entry creation, update, and destruction. These 
functions are all called before the modification has taken place and can abort 
the operation.
-
-You can also use cache writers to store data that you want to make persistent.
-
-## <a id="application-plugins__section_3F43B898CD254076B4DD777E9B4CC8F0" 
class="no-quick-link"></a>CacheListener
-
-A cache listener is an application plug-in that asynchronously handles changes 
to a region's contents. A cache listener has callback functions to handle 
region destruction and invalidation, along with entry creation, update, 
invalidation, and destruction. These functions are called asynchronously after 
the modification has taken place.
-
-This declarative XML example establishes a cache listener when a region is 
created:
-
-``` pre
-<region name="region11">
-    <region-attributes>
-        <cache-listener library-name="appl-lib"
-            library-function-name ="createCacheListener" />
-    </region-attributes>
-</region>
-```
-
-Unlike cache loaders and cache writers, cache listeners only receive events 
for entries to which the client has performed operations or registered interest.
-
-When the listener is attached to a region with caching disabled, the old value 
is always `NULL`.
-
-**Note:**
-Do not perform region operations inside the cache listener. Once you have 
configured a cache listener, the event supplies the new entry values to the 
application. Performing a get with a key from the `EntryEvent` can result in 
distributed deadlock. For more about this, see the online API documentation for 
`EntryEvent`.
-
-When a region disconnects from a cache listener, you can implement the 
`afterRegionDisconnected` callback event. This callback event is only be 
invoked when using the `pool` API and `subscription` is enabled on the pool. 
For example:
-
-``` pre
-class DisconnectCacheListener : public CacheListener
-{
-    void afterRegionDisconnected( const RegionPtr& region )
-    {
-        printf("After Region Disconnected event received");
-    }
-};
-```
-
-## <a id="application-plugins__section_348E00A84F274D4B9DBA9ECFEB2F012E" 
class="no-quick-link"></a>PartitionResolver
-
-This section pertains to data access in server regions that have custom 
partitioning. Custom partitioning uses a Java `PartitionResolver` to colocate 
like data in the same buckets. For the client, you can use a 
`PartitionResolver` that matches the server's implementation to access data in 
a single hop. With single-hop data access, the client pool maintains 
information on where a partitioned region's data is hosted. When accessing a 
single entry, the client directly contacts the server that hosts the key--in a 
single hop.
-
-**Note:**
-Single hop is used for the following operations: `put`, `get`, `destroy`, 
`putAll`, `getAll`, `removeAll` and `onRegion` function execution.
-
-**Implementing Single-Hop on a Partitioned Region**
-
-1.  Make sure the pool attribute, `pr-single-hop-enabled`, is set to `true` or 
not set. It is `true` by default.
-2.  If the server uses a custom `PartitionResolver` install an implementation 
of `PartitionResolver` in the client region that returns, entry for entry, the 
same value as the server's Java `PartitionResolver` implementation. The server 
uses the resolver to colocate like data within a partitioned region.
-
-    If the server does not use a custom resolver, the default resolvers in 
client and server match, so single hop will work there by default.
-
-Disable single hop behavior for a region by setting its pool attribute 
`pr-single-hop-enabled` to `false`.
-
-See [&lt;client-cache&gt; Element 
Reference](../../reference/topics/client-cache.html) for information on setting 
`pr-single-hop-enabled`.
-
-See [Partitioned 
Regions](../../developing/partitioned_regions/chapter_overview.html) for more 
information, including colocating like data within a partitioned region and how 
to get the best performance with PR single hop.
-
-**Implementing a PartitionResolver**
-
-See [Custom-Partitioning and Colocating 
Data](../../developing/partitioned_regions/overview_custom_partitioning_and_data_colocation.html)
 for information on custom-partitioning the server partitioned regions.
-
-1.  Implement `PartitionResolver` in the same place that you did in the 
server--custom class, key, or cache callback argument.
-2.  Program the resolver's functions the same way you programmed them in the 
Java implementation. Your implementation must match the server's.
-
-    Example of programming the `PartitionResolver` in C++:
-
-    ``` pre
-    class TradeKeyResolver : public PartitionResolver
-    {
-    private:
-        string m_tradeID;
-        int m_month;
-        int m_year;
-    public:
-        TradeKeyResolver() { }
-        TradeKeyResolver(int month, int year) {
-            m_month = month;
-            m_year = year;
-        }
-
-        ~TradeKeyResolver() { }
-
-        static PartitionResolverPtr createTradeKeyResolver() {
-            PartitionResolverPtr tradeKeyResolver( new TradeKeyResolver());
-        return tradeKeyResolver;
-        }
-        const char* getName() {
-            return "TradeKey";
-        }
-        CacheableKeyPtr getRoutingObject(const EntryEvent& opDetails) {
-            return CacheableKey::create(m_month + m_year);
-        }
-    };
-    ```
-
-    Example of programming the `PartitionResolver` in C\#:
-
-    ``` pre
-    using System;
-    using System.Threading;
-    // Use the GemFire namespace
-    using GemStone.GemFire.Cache;
-    class TradeKeyResolver : IPartitionResolver
-    {
-        private int m_month = 0;
-        private int m_year = 0;
-
-        public static TradeKeyResolver CreateTradeKeyResolver()
-        {
-            return new TradeKeyResolver();
-        }
-
-        public virtual ICacheableKey GetRoutingObject(EntryEvent entry)
-        {
-            return new CacheableInt32(m_month + m_year);
-        }
-
-        public virtual String GetName()
-        {
-            return "TradeKeyResolver";
-        }
-    }
-    ```
-
-3.  Install the resolver in the region. Use one of these methods:
-
-    XML partition resolver declaration:
-
-    ``` pre
-    <region name="trades" refid="CACHING_PROXY">
-        <region-attributes>
-            <partition-resolver library-name="appl-lib" library-function-name=
-            "createTradeKeyResolver"/>
-        </region-attributes>
-    </region>
-    <pool free-connection-timeout="12345" idle-timeout="5555"
-            load-conditioning-interval="23456" max-connections="7"
-            min-connections="3" name="test_pool_1" ping-interval="12345"
-            read-timeout="23456" retry-attempts="3" server-group="ServerGroup1"
-            socket-buffer-size="32768" statistic-interval="10123"
-            subscription-ack-interval="567" subscription-enabled="true"
-            subscription-message-tracking-timeout="900123"
-            subscription-redundancy="0" thread-local-connections="5"
-            pr-single-hop-enabled="true" >
-        <locator host="localhost" port="34756"/>
-    </pool>
-    ```
-
-    Programmatic partition resolver installation:
-
-    ``` pre
-    void setPartitionResolver()
-    {
-        CachePtr cachePtr = CacheFactory::createCacheFactory()->create();
-        PartitionResolverPtr resolver( new TradeKeyResolver());
-        RegionFactoryPtr regionFactory =
-            cachePtr->createRegionFactory(PROXY)
-            ->setClientNotificationEnabled(true)
-            ->setPartitionResolver(resolver);
-        RegionPtr regionPtr = regionFactory->create( "Trades" );
-    }
-    ```
-
-Your implementation of `PartitionResolver` must match that of the server side.
-
-## <a id="application-plugins__section_4EC30A57C37E4DDF83990A264D2C0284" 
class="no-quick-link"></a>Using AttributesMutator to Modify a Plug-In
-
-A cache listener, cache loader or cache writer can be added to or removed from 
a region after the region is created by retrieving and running the `Region` 
object's `AttributesMutator`. Mutable attributes define operations that are run 
from the client itself.
-
-This example shows how to use `AttributesMutator` to dynamically add a cache 
listener to an existing region.
-
-``` pre
-void setListener(RegionPtr& region)
-{
-    CacheListenerPtr regionListener = new TestCacheListener();
-    AttributesMutatorPtr regionAttributesMutator =
-        region->getAttributesMutator();
- 
-    // Change cache listener for region.
-    regionAttributesMutator->setCacheListener(regionListener);
-}
-```
-
-The plug-ins can also be implemented using a dynamically linked library. The 
class is not available to the application code in this case, so a `factory` 
method is required by the `set` function along with the name of the library.
-
-This example shows how to use `AttributesMutator` along with the 
`setCacheListener` function to obtain a new cache listener object using the 
`factory` function provided by the library. Next, the listener is set for the 
region.
-
-``` pre
-void setListenerUsingFactory(RegionPtr& region)
-{
-    AttributesMutatorPtr regionAttributesMutator =
-    region->getAttributesMutator();
-
-    // Change cache listener for region.
-    regionAttributesMutator->setCacheListener("Library", 
"createTestCacheListener");
-}
-```
-
-To use `AttributesMutator` to remove a plug-in from a region, set the 
plug-in's value to `NULLPTR`, as shown in the following example.
-
-``` pre
-void removeListener(RegionPtr& region)
-{
-    CacheListenerPtr nullListener = NULLPTR;
-    AttributesMutatorPtr regionAttributesMutator =
-        region->getAttributesMutator();
-
-    // Change cache listener for region to NULLPTR
-    regionAttributesMutator->setCacheListener(nullListener);
-}
-```
-
-## <a id="application-plugins__section_428DCC57B6344603AA19DCAFCE483A10" 
class="no-quick-link"></a>Considerations for Implementing Callbacks
-
-Keep your callback implementations lightweight and prevent situations that 
might cause them to hang. For example, do not perform distribution operations 
or disconnects inside events.
-
-Your code should handle any exceptions that it generates. If not, Geode 
handles them as well as possible. Because C++ has no standard for exceptions, 
in many cases Geode can only print an `unknown error` message.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/cache-management.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/cache-management.html.md.erb 
b/geode-docs/nativeclient/client-cache/cache-management.html.md.erb
deleted file mode 100644
index 1f9004d..0000000
--- a/geode-docs/nativeclient/client-cache/cache-management.html.md.erb
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title:  Cache Management
----
-
-This section covers cache management.
-
-<a id="using-thread-safety__section_165DAD3CE6CA44D9A883FC91D4F09343"></a>
-
--   **[Client-to-Server Connection 
Process](../../nativeclient/client-cache/client-to-server-connection.html)**
-
-    It is important to understand the sequence of events that occur when the 
native client connects with a Geode cache server.
-
--   **[Controlling Cache 
Size](../../nativeclient/client-cache/controlling-cache-size.html)**
-
-    You can control cache size through region size limits, cache size limits, 
or a combination of the two.
-
--   **[Managing the Lifetime of a Cached 
Object](../../nativeclient/client-cache/managing-lifetime-cached-object.html)**
-
-    All cacheable objects derive from `SharedBase` , which provides reference 
counting. Cacheable objects are referenced using `SharedPtr` types.
-
--   **[Using Thread Safety in Cache 
Management](../../nativeclient/client-cache/using-thread-safety.html)**
-
-    When you perform structural changes on your cache, such as creating or 
closing a `Cache`, `Pool`, or `Region`, synchronize your operations or do them 
in a single thread.
-
--   **[Troubleshooting](../../nativeclient/client-cache/troubleshooting.html)**
-
-    This section provides troubleshooting information for the native client.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/cache-ownership.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/cache-ownership.html.md.erb 
b/geode-docs/nativeclient/client-cache/cache-ownership.html.md.erb
deleted file mode 100644
index 37f010c..0000000
--- a/geode-docs/nativeclient/client-cache/cache-ownership.html.md.erb
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title:  Local, Remote, and Distributed Caches
----
-
-The *distributed system* defines how native client and cache server processes 
find each other.
-
-The distributed system keeps track of its membership list and makes its 
members aware of the identities of the other members in the distributed system.
-
-A cache for a native client is referred to as its *local cache*. All other 
caches in the distributed system are considered *remote caches* to the 
application. Every cache server and application process has its own cache. The 
term *distributed cache* is used to describe the union of all caches in a Geode 
distributed system.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/caches.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/caches.html.md.erb 
b/geode-docs/nativeclient/client-cache/caches.html.md.erb
deleted file mode 100644
index cfc456c..0000000
--- a/geode-docs/nativeclient/client-cache/caches.html.md.erb
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title:  Caches
----
-
-The cache is the entry point to native client data caching in Geode. Through 
the cache, native clients gain access to the Geode caching framework for data 
loading, distribution, and maintenance.
-
--   **[About the Native Client 
Cache](../../nativeclient/client-cache/overview-client-cache.html)**
-
-    The cache consists of data regions, each of which can contain any number 
of entries. Region entries hold the cached data. Every entry has a key that 
uniquely identifies it within the region and a value where the data object is 
stored.
-
--   **[Cache APIs](../../nativeclient/client-cache/caching-apis.html)**
-
-    The native client has two cache APIs, `RegionService` and `Cache`.
-
--   **[Local, Remote, and Distributed 
Caches](../../nativeclient/client-cache/cache-ownership.html)**
-
-    The *distributed system* defines how native client and cache server 
processes find each other.
-
--   **[Creating and Accessing a 
Cache](../../nativeclient/client-cache/create-access-cache.html)**
-
-    When you create a native client cache, you are creating a native client 
cache instance. You must provide some basic configuration information such as a 
connection name and cache initialization parameters for the native client's 
cache instance.
-
--   **[Closing the Cache](../../nativeclient/client-cache/closing-cache.html)**
-
-    Use the `Cache::close` function to release system resources when you 
finish using the cache.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/caching-apis.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/caching-apis.html.md.erb 
b/geode-docs/nativeclient/client-cache/caching-apis.html.md.erb
deleted file mode 100644
index 455fbf0..0000000
--- a/geode-docs/nativeclient/client-cache/caching-apis.html.md.erb
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title:  Cache APIs
----
-
-The native client has two cache APIs, `RegionService` and `Cache`.
-
-## <a id="caching-apis__section_8F81996678B64BBE94EF352527F7F006" 
class="no-quick-link"></a>RegionService API
-
-`RegionService` provides:
-
--   Access to existing cache regions.
--   Access to the standard query service for the cache, which sends queries to 
the servers. See [Remote 
Querying](../remote-querying/remote-querying.html#security) and [Continuous 
Querying](../continuous-querying/continuous-querying.html#security).
-
-`RegionService` is inherited by `Cache`.
-
-You do not use instances of `RegionService` except for secure client 
applications with many users. See [Creating Multiple Secure User Connections 
with RegionService](../security/createsecureconnregionservice.html#security).
-
-## <a id="caching-apis__section_403383B9B5044A939A89A5BBB4915452" 
class="no-quick-link"></a>Cache API
-
-Use the `Cache` to manage your client caches. You have one `Cache` per client.
-
-The `Cache` inherits `RegionService` and adds management of these client 
caching features:
-
--   Region creation.
--   Subscription keepalive management for durable clients.
--   Access to the underlying distributed system.
--   `RegionService` creation for secure access by multiple users.
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/caching-enabled.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/caching-enabled.html.md.erb 
b/geode-docs/nativeclient/client-cache/caching-enabled.html.md.erb
deleted file mode 100644
index 1ce9960..0000000
--- a/geode-docs/nativeclient/client-cache/caching-enabled.html.md.erb
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title:  CachingEnabled
----
-
-This attribute determines whether data is cached in this region. For example, 
you might choose to configure the distributed system as a simple messaging 
service where clients run without a cache.
-
-**Note:**
-You can configure the most common of these options with the predefined region 
attributes. See [RegionShortcuts](region-shortcuts.html#region-shortcuts) and 
the Javadocs for `RegionShortcut`.
-
-If `CachingEnabled` is false (no caching), an `IllegalStateException` is 
thrown if any of these attributes are set:
-
--   [InitialCapacity](initial-capacity.html#initial-capacity)
--   `EntryTimeToLive` under [Specifying Expiration 
Attributes](expiration-attributes.html#expiration-attributes)
--   `EntryIdleTimeout` under [Specifying Expiration 
Attributes](expiration-attributes.html#expiration-attributes)
--   [LoadFactor](load-factor.html#load-factor)
--   [ConcurrencyLevel](concurrency-level.html#concurrency-level)
--   
[LruEntriesLimit](lru-entries-limit.html#concept_75D723D60E044FF9AE97C939699AB10A)
--   [DiskPolicy](disk-policy.html#disk-policy)
-
-The following declaration enables caching for the region:
-
-``` pre
-<region-attributes caching-enabled="true"> 
-</region-attributes>
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/chapter-overview.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/chapter-overview.html.md.erb 
b/geode-docs/nativeclient/client-cache/chapter-overview.html.md.erb
deleted file mode 100644
index d898928..0000000
--- a/geode-docs/nativeclient/client-cache/chapter-overview.html.md.erb
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title:  Configuring the Native Client Cache
----
-
-*Configuring the Native Client Cache* describes the native client cache 
functionality, initialization file, and APIs. It provides information about 
creating and working with caches, cache regions, and region entries.
-
-The native client cache provides a framework for native clients to store, 
manage, and distribute application data.
-
--   **[Caches](../../nativeclient/client-cache/caches.html)**
-
-    The cache is the entry point to native client data caching in Geode. 
Through the cache, native clients gain access to the Geode caching framework 
for data loading, distribution, and maintenance.
-
--   **[Cache Initialization File 
(cache.xml)](../../nativeclient/cache-init-file/chapter-overview.html)**
-
-    To ease the task of managing the structure of the cache, you can define 
the default Geode cache structure in an XML-based initialization file.
-
--   **[Regions](../../nativeclient/client-cache/regions.html)**
-
-    You create cache regions either programmatically or through declarative 
statements in the `cache.xml` file. Generally, a cache is organized and 
populated through a combination of the two approaches.
-
--   **[Region Entries](../../nativeclient/client-cache/entries.html)**
-
-    Region entries hold cached application data. Entries are automatically 
managed according to region attribute settings.
-
--   **[Region 
Consistency](../../nativeclient/client-cache/consistency_checking_in_regions.html)**
-
-    Geode ensures that all copies of a region eventually reach a consistent 
state on all members and clients that host the region.
-
--   **[Region 
Attributes](../../nativeclient/client-cache/region-attributes.html)**
-
-    Region attributes govern the automated management of a region and its 
entries.
-
--   **[Cache 
Management](../../nativeclient/client-cache/cache-management.html)**
-
-    This section covers cache management.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/client-to-server-connection.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/client-to-server-connection.html.md.erb 
b/geode-docs/nativeclient/client-cache/client-to-server-connection.html.md.erb
deleted file mode 100644
index e2008a5..0000000
--- 
a/geode-docs/nativeclient/client-cache/client-to-server-connection.html.md.erb
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title:  Client-to-Server Connection Process
----
-
-It is important to understand the sequence of events that occur when the 
native client connects with a Geode cache server.
-
-<a 
id="client-to-server-connection__section_C1E805D842FD44B984041C2ED1D4C2EF"></a>
-
-1.  A native client region is configured in `cache.xml` or programmatically 
with a set of server connection endpoints. Server endpoints identify each cache 
server by specifying the server's name and port number.
-
-    Client threads obtain, use, and release a connection to a connection pool 
that maintains new connections. The number of connections that a client can 
establish is governed by the pool's `min-connections` and `max-connections` 
settings, either using client XML configuration or programmatically through the 
`CacheFactory::setMinConnections()` and `CacheFactory::setMaxConnections()` 
APIs. The defaults for `min-connections` is 1 and `max-connections` is -1 
meaning the connection count can grow to accommodate the number of active 
threads performing region operations.
-
-    This example shows how to use `cache.xml` to configure a native client 
region with endpoints set to two cache servers:
-
-    ``` pre
-    <pool name="examplePool" subscription-enabled="true" >
-        <server host="java_servername1" port="java_port1" />
-        <server host="java_servername2" port="java_port2" />
-    </pool>
-    <region name="NativeClientRegion" refid="CACHING_PROXY">
-        <region-attributes pool-name="examplePool"/>
-    </region>
-    ```
-    TCP connections on the native client are specified at the cache level, or 
by overriding endpoints for specific regions. The connections are created as 
the regions are created. In addition, connections can also get created for 
querying without having any created regions. In this case, when endpoints are 
defined at the cache level no regions are yet created and a query is fired.
-
-    You can configure client-server connections in two ways. Use either the 
region/cache endpoints or the Pool API. For more information about the pool 
API, see [Using Connection 
Pools](../connection-pools/connection-pools.html#using-connection-pools).
-
-2.  The client announces to the server which entries it wishes to have updated 
by programmatically registering interest in those entries. See [Registering 
Interest for 
Entries](registering-interest-for-entries.html#registering-interest-for-entries)
 for more information.
-
-3.  The client `cache.xml` file should have the following parameters 
configured so the client can update the server and the client can receive 
updates from the server:
-    -   Caching enabled in the client region, by using the `CACHING_PROXY 
RegionShortcut` setting in the region attribute `refid`. A listener could also 
be defined so event notification occurs. You can use both, but at least one of 
the two methods must be used by the client to receive event notifications.
-    -   Set `subscription-enabled` to `true` so the client receives update 
notifications from the server for entries to which it has registered interest.
-
-4.  A native client application calls the C++ or .NET API to connect to a 
cache server.
-5.  The client and the cache server exchange a handshake over a configured 
endpoint to create a connection.
-6.  Any `create`, `put`, `invalidate`, and `destroy` events sent to the server 
are propagated across the distributed cache so the client can receive the 
events.
-
-**Note:**
-You may be able to improve system performance by making adjustments to the 
cache server.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/closing-cache.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/closing-cache.html.md.erb 
b/geode-docs/nativeclient/client-cache/closing-cache.html.md.erb
deleted file mode 100644
index fcd53e2..0000000
--- a/geode-docs/nativeclient/client-cache/closing-cache.html.md.erb
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title:  Closing the Cache
----
-
-Use the `Cache::close` function to release system resources when you finish 
using the cache.
-
-After the cache is closed, any further method calls on the cache or any region 
object result in a `CacheClosedException` .
-
-If the cache is in a durable client, you need to use the `keepalive` version 
of the close method. See [Disconnecting From the 
Server](../preserving-data/disconnecting-from-server.html#concept_3A9AC62F96FA44DBBB5CCBFD3EA19B56).
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/concurrency-checks-enabled.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/concurrency-checks-enabled.html.md.erb 
b/geode-docs/nativeclient/client-cache/concurrency-checks-enabled.html.md.erb
deleted file mode 100644
index 5c81fa6..0000000
--- 
a/geode-docs/nativeclient/client-cache/concurrency-checks-enabled.html.md.erb
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title:  ConcurrencyChecksEnabled
----
-
-This attribute determines whether members perform checks to provide consistent 
handling for concurrent or out-of-order updates to distributed regions.
-
-A client cache can disable consistency checking for a region even if server 
caches enable consistency checking for the same region. This configuration 
ensures that the client sees all events for the region, but it does not prevent 
the client cache region from becoming out-of-sync with the server cache.
-
-Optionally enable concurrency checks for the region. Example:
-
-``` pre
-<region-attributes concurrency-checks-enabled="true"> 
-</region-attributes>
-```
-
-See [Region 
Consistency](consistency_checking_in_regions.html#concept_77340A4999AC4861972A0EE10303E557)
 for more information.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/concurrency-level.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/concurrency-level.html.md.erb 
b/geode-docs/nativeclient/client-cache/concurrency-level.html.md.erb
deleted file mode 100644
index 08e0582..0000000
--- a/geode-docs/nativeclient/client-cache/concurrency-level.html.md.erb
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title:  ConcurrencyLevel
----
-
-<a id="concurrency-level__section_20FB0B9EEE9442BAAD87E3C488610866"></a>
-This attribute estimates the maximum number of application threads that 
concurrently access a region entry at one time. This attribute helps optimize 
the use of system resources and reduce thread contention.
-
-The following declaration sets the region's `ConcurrencyLevel` to `16`:
-
-``` pre
-<region-attributes concurrency-level="16">
-</region-attributes>
-```
-
-**Note:**
-When `CachingEnabled` is `false`, do not set the `ConcurrencyLevel` attribute. 
An `IllegalStateException` is thrown if the attribute is set.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/consistency_checking_in_regions.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/consistency_checking_in_regions.html.md.erb
 
b/geode-docs/nativeclient/client-cache/consistency_checking_in_regions.html.md.erb
deleted file mode 100644
index 87c3303..0000000
--- 
a/geode-docs/nativeclient/client-cache/consistency_checking_in_regions.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title:  Region Consistency
----
-
-Geode ensures that all copies of a region eventually reach a consistent state 
on all members and clients that host the region.
-
-By default Geode members perform consistency checks when they apply updates to 
a distributed region, in order to ensure that all copies of the region 
eventually become consistent on all Geode members and client caches that host 
the region. Different types of region ensure consistency using different 
techniques. However, when consistency checking is enabled (the default) all 
entries in a region require additional overhead in order to store version and 
timestamp information.
-
-Although a region must have the same consistency checking configuration on all 
Geode members that host the region, you can optionally disable consistency 
checking in a client cache region while leaving consistency checking enabled 
for the region on Geode members. This configuration may be necessary in certain 
cases where the client must view all updates to a given region, even when Geode 
members discards an update in order to preserve region consistency.
-
-See [Consistency for Region 
Updates](../../developing/distributed_regions/region_entry_versions.html#topic_CF2798D3E12647F182C2CEC4A46E2045)
 for more information.
-
-## <a 
id="concept_77340A4999AC4861972A0EE10303E557__section_167CD194A5374C64B4064783490F3EA8"
 class="no-quick-link"></a>Native Client Overhead for Consistency Checks
-
-In the native client regions, the overhead for performing consistency check is 
an additional 11 bytes per region entry. This overhead is slightly smaller than 
the overhead required to provide consistency checking on server-side region 
entries.
-
-If you cannot support the additional overhead in your deployment, you can 
disable consistency checks by setting the region attribute 
`concurrency-checks-enabled` to false for each region hosted by your client.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/controlling-cache-size.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/controlling-cache-size.html.md.erb 
b/geode-docs/nativeclient/client-cache/controlling-cache-size.html.md.erb
deleted file mode 100644
index e67b5ac..0000000
--- a/geode-docs/nativeclient/client-cache/controlling-cache-size.html.md.erb
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title:  Controlling Cache Size
----
-
-You can control cache size through region size limits, cache size limits, or a 
combination of the two.
-
-<a id="controlling-cache-size__section_A0C25D6D1D5243778800AE67CAD8CB2C"></a>
-Geode controls region size by moving least recently used (LRU) entries from 
the region or from all cache regions.
-
-## <a id="controlling-cache-size__section_3C7994A4C9D9468F860D99C0ED086D74" 
class="no-quick-link"></a>Controlling Region Size
-
-You can cap the size of any region with the region attribute 
[LruEntriesLimit](lru-entries-limit.html#concept_75D723D60E044FF9AE97C939699AB10A).
 You can specify whether to destroy the entries or overflow them to disk in the 
attribute [DiskPolicy](disk-policy.html#disk-policy). If you overflow entries 
to disk, you must also specify the attribute 
[PersistenceManager](persistence-manager.html#persistence-manager).
-
-## <a id="controlling-cache-size__section_E59CA4D5724147DC83E8991E654AC155" 
class="no-quick-link"></a>Controlling Cache Size
-
-You can control overall cache size with the 
[heap-lru-limit](../setting-properties/attributes-gfcpp.html#attributes-gfcpp), 
which is set in `gfcpp.properties`. This property sets the maximum amount of 
memory used for the cache, in megabytes. If a new entry causes memory to grow 
past this limit, the LRU algorithm is called to evict entries. Heap LRU causes 
eviction to occur on all regions in the cache, overriding region-level 
[LruEntriesLimit](lru-entries-limit.html#concept_75D723D60E044FF9AE97C939699AB10A)
 settings when it needs to reclaim memory.
-
-For each region, evictions are performed according to the region's 
`DiskPolicy` and `PersistenceManager` settings. If you use `heap-lru-limit`, 
review these region attributes for all your caching regions, to be sure you are 
evicting the way you want to.
-
-The related 
[heap-lru-delta](../setting-properties/attributes-gfcpp.html#attributes-gfcpp) 
property, also set in `gfcpp.properties`, is the amount of memory to free up 
once the LRU evictions have begun. Memory is reclaimed until the amount of 
memory used is below `heap-lru-limit` minus `heap-lru-delta`.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/create-access-cache.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/create-access-cache.html.md.erb 
b/geode-docs/nativeclient/client-cache/create-access-cache.html.md.erb
deleted file mode 100644
index b0fde6f..0000000
--- a/geode-docs/nativeclient/client-cache/create-access-cache.html.md.erb
+++ /dev/null
@@ -1,53 +0,0 @@
----
-title:  Creating and Accessing a Cache
----
-
-When you create a native client cache, you are creating a native client cache 
instance. You must provide some basic configuration information such as a 
connection name and cache initialization parameters for the native client's 
cache instance.
-
-When you create a cache, you provide the following input:
-
--   **Connection name**. Used in logging to identify both the distributed 
system connection and the cache instance. If you do not specify a connection 
name, a unique (but non-descriptive) default name is assigned.
--   **`cache.xml` to initialize the cache (if the initialization is not done 
programmatically)**. To modify the cache structure, edit `cache.xml` in your 
preferred text editor. No changes to the application code are required. If you 
do not specify a cache initialization file, you need to initialize the cache 
programmatically.
-
-The `cache.xml` file contains XML declarations for cache, region, and region 
entry configuration.
-
-This XML declares server connection pools and regions:
-
-``` pre
-<cache>
-  <region name="clientRegion1" refid="PROXY">
-    <region-attributes pool-name="serverPool1"/>
-  </region>
-  <region name="clientRegion2" refid="PROXY">
-    <region-attributes pool-name="serverPool2"/>
-  </region>
-  <region name="localRegion3" refid="LOCAL"/>
-  <pool name="serverPool1">
-    <locator host="host1" port="40404"/>
-  </pool>
-  <pool name="serverPool2">
-    <locator host="host2" port="40404"/>
-  </pool>
-</cache>
-    
-```
-
-When you use the regions, the client regions connect to the servers through 
the pools named in their configurations.
-
-This file can have any name, but is generally referred to as `cache.xml` .
-
-For a list of the parameters in the `cache.xml` file, including the DTD, see 
[Cache Initialization 
File](../cache-init-file/chapter-overview.html#chapter-overview).
-
-To create your cache, call the `CacheFactory create` function.
-
-The `cache` object it returns gives access to the native client caching API. 
For example:
-
-``` pre
-CacheFactoryPtr cacheFactory = CacheFactory::createCacheFactory();
-CachePtr cachePtr = cacheFactory->create();
-    
-```
-
-**Note:** For more information on how to create a cache, see [Pivotal GemFire 
Native Client C++ 
API](../cpp-caching-api/cpp-caching-api.html#concept_CEC658A999414AC3A494578C214BF64E)
 or [Pivotal GemFire Native Client .NET 
API](../dotnet-caching-api/dotnet-caching-api.html#concept_FC6776DCE6ED48B887A6137761104AA4).
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/declarative-region-creation.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/declarative-region-creation.html.md.erb 
b/geode-docs/nativeclient/client-cache/declarative-region-creation.html.md.erb
deleted file mode 100644
index 5c018c1..0000000
--- 
a/geode-docs/nativeclient/client-cache/declarative-region-creation.html.md.erb
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title:  Declarative Region Creation
----
-
-Declarative region creation involves placing the region's XML declaration, 
with the appropriate attribute settings, in the `cache.xml` file that is loaded 
at cache creation.
-
-**Note:**
-Before creating a region, specify region attributes. See [Region 
Attributes](region-attributes.html#region-attributes).
-
-Regions are placed inside the cache declaration in `region` elements. For 
example:
-
-``` pre
-<cache>
-  <pool name="examplePool" subscription-enabled="true" >
-    <server host="localhost" port="40404" />
-  </pool>
-  <region name="A" refid="PROXY">
-    <region-attributes pool-name="examplePool"/>
-  </region>
-  <region name="A1">
-    <region-attributes refid="PROXY" pool-name="examplePool"/>
-  </region>
-  <region name="A2" refid="CACHING_PROXY">
-    <region-attributes pool-name="examplePool">
-      <region-time-to-live>
-        <expiration-attributes timeout="120" action="invalidate"/>
-      </region-time-to-live>
-    </region-attributes>
-  </region>
-</cache>
-    
-```
-
-The `cache.xml` file contents must conform to the DTD provided in the 
`productDir/dtd/gfcpp-cache8000.dtd` file. For details, see [Cache 
Initialization File](../cache-init-file/chapter-overview.html#chapter-overview).
-
-**Note:** For more information on how to create a region, see [Working with 
the C++ 
API](../cpp-caching-api/cpp-caching-api.html#concept_CEC658A999414AC3A494578C214BF64E),
 [Working with the .NET 
API](../dotnet-caching-api/dotnet-caching-api.html#concept_FC6776DCE6ED48B887A6137761104AA4),
 and the native client API reference.
-
-


Reply via email to