http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb 
b/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb
deleted file mode 100644
index d862004..0000000
--- a/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title:  DiskPolicy
----
-
-<a id="disk-policy__section_F3A921FC67B44DD795BD9B5C180FCBB1"></a>
-If the `lru-entries-limit` attribute is greater than zero, the optional 
`disk-policy` attribute determines how over-limit LRU entries are handled. LRU 
entries over the limit are either destroyed by default (`disk-policy` is none ) 
or written to disk (`overflows`).
-
-**Note:**
-If `LruEntriesLimit` is `0`, or `CachingEnabled` is `false`, do not set the 
`disk-policy` attribute. An `IllegalStateException` is thrown if the attribute 
is set.
-
-This declaration causes LRU to overflow to disk:
-
-``` pre
-<region-attributes lru-entries-limit="20000"
-    disk-policy="overflows">
-  <persistence-manager ... />
-</region-attributes>
-```
-
-Overflow requires a persistence manager for cache-to-disk and disk-to-cache 
operations. See 
[PersistenceManager](persistence-manager.html#persistence-manager).
-
-## <a id="disk-policy__section_FE325E59644149ACA43DA2ABB4CF0F7A" 
class="no-quick-link"></a>Overflowing Data to Disk
-
-Region data can be stored to disk using the overflow process to satisfy region 
capacity restrictions without completely destroying the local cache data. The 
storage mechanism uses disk files to hold region entry data. When an entry is 
overflowed, its value is written to disk but its key and entry object remain in 
the cache. This also uses the region attribute 
[DiskPolicy](disk-policy.html#disk-policy).
-
-Overflow allows you to keep the region within a user-specified size in memory 
by relegating the values of least recently used (LRU) entries to disk. Overflow 
essentially uses disk as a swap space for entry values. When the region size 
reaches the specified threshold, entry values are moved from memory to disk, as 
shown in the following figure. If an entry is requested whose value is only on 
disk, the value is copied back into memory, possibly causing the value of a 
different LRU entry to be overflowed to disk.
-
-<a id="disk-policy__fig_67963EC3BDD64272BBDAD9517E1D78A0"></a>
-
-<span class="figtitleprefix">Figure: </span>Data Flow Between Overflow Region 
and Disk Files
-
-<img src="../common/images/client-cache-data-flow.gif" alt="Data Flow Between 
Overflow Region and Disk Files" 
id="disk-policy__image_687021ECD97A40FB843DBDE59C555384" class="image" />
-
-In this figure the value of the LRU entry X has been moved to disk to recover 
space in memory. The key for the entry remains in memory. From the distributed 
system perspective, the value on disk is as much a part of the region as the 
data in memory. A `get` performed on region B looks first in memory and then on 
disk as part of the local cache search.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/entries.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/entries.html.md.erb 
b/geode-docs/nativeclient/client-cache/entries.html.md.erb
deleted file mode 100644
index b5799f5..0000000
--- a/geode-docs/nativeclient/client-cache/entries.html.md.erb
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title:  Region Entries
----
-
-Region entries hold cached application data. Entries are automatically managed 
according to region attribute settings.
-
-You can create, update, invalidate, and destroy entries through explicit API 
calls or through operations distributed from other caches.
-
-When the number of entries is very large, a partitioned region can provide the 
required data management capacity if the total size of the data is greater than 
the heap in any single JVM.
-
-When an entry is created, a new object is instantiated in the region 
containing:
-
--   The entry key.
--   The entry value. This is the application data object. The entry value may 
be set to `NULL`, which is the equivalent of an invalid value.
-
-Entry operations invoke callbacks to user-defined application plug-ins. In 
this chapter, the calls that may affect the entry operation itself (by 
providing a value or aborting the operation, for example) are highlighted, but 
all possible interactions are not listed. For details, see [Application 
Plug-Ins](application-plugins.html#application-plugins).
-
-`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.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb 
b/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb
deleted file mode 100644
index d154d62..0000000
--- a/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title:  Specifying Expiration Attributes
----
-
-<a id="expiration-attributes__section_4901B92DE7EB408F81792920C9E4ED7C"></a>
-Expiration attributes govern the automatic eviction of regions and region 
entries from the cache. Eviction is based on the time elapsed since the last 
update or access to the object. This is referred to as the least-recently-used 
(LRU) eviction process. Expiration options range from marking the expired 
object as invalid to completely removing it from the distributed cache. 
Eviction can help keep data current by removing outdated entries, prompting a 
reload the next time they are requested. Eviction may also be used to recover 
space in the cache by clearing out unaccessed entries and regions.
-
-Similar to application plug-ins, expiration activities are hosted by each 
application that defines a region in its cache.
-
-The following example shows a declaration that causes the region's entries to 
be invalidated in the local cache after they have not been accessed for one 
minute.
-
-``` pre
-<region-attributes>
-    <entry-idle-time>
-        <expiration-attributes timeout="60" action="local-invalidate"/>
-    </entry-idle-time>
-</region-attributes>
-```
-
-Region and region entry expiration attributes are set at the region level. By 
default, regions and entries do not expire. The following attributes cover two 
types of expiration: time-to-live (TTL) and idle timeout.
-
-<table>
-<colgroup>
-<col width="50%" />
-<col width="50%" />
-</colgroup>
-<tbody>
-<tr class="odd">
-<td><code class="ph codeph">RegionTimeToLive</code></td>
-<td>Number of seconds that the region remains in the cache after the last 
creation or update before the expiration action occurs.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">EntryTimeToLive</code></td>
-<td>For entries, the counter is set to zero for <code class="ph 
codeph">create</code> and <code class="ph codeph">put</code> operations. Region 
counters are reset when the region is created and when an entry has its counter 
reset. An update to an entry causes the time-to-live (TTL) counters to be reset 
for the entry and its region.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">RegionIdleTimeout</code></td>
-<td>Number of seconds that the region remains in the cache after the last 
access before the expiration action occurs.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">EntryIdleTimeout</code></td>
-<td>The idle timeout counter for an object is reset when its TTL counter is 
reset. An entry's idle timeout counter is also reset whenever the entry is 
accessed through a <code class="ph codeph">get</code> operation.
-<p>The idle timeout counter for a region is reset whenever the idle timeout is 
reset for one of its entries.</p></td>
-</tr>
-</tbody>
-</table>
-
-## <a id="expiration-attributes__section_F338C1117B7B44398F59523B881EDD55" 
class="no-quick-link"></a>Using Statistics to Measure Expiration
-
-Expiration is measured by comparing expiration attribute settings with the 
last accessed time and last modified time statistics. These statistics are 
directly available to applications through the `CacheStatistics` object that is 
returned by the `Region::getStatistics` and `RegionEntry::getStatistics` 
functions. The `CacheStatistics` object also provides a function for resetting 
the statistics counters.
-
-## <a id="expiration-attributes__section_6B402F97ECD8492A8798AC838D0BB606" 
class="no-quick-link"></a>Expiration Actions
-
-You can specify one of the following actions for each expiration attribute:
-
--   **Destroy**. Removes the object completely from the cache. For regions, 
all entries are destroyed as well. Destroy actions are distributed according to 
the region's distribution settings.
--   **Invalidate**. Marks the object as invalid. For entries, the value is set 
to `NULL`. You invalidate a region by invalidating all its entries. Invalidate 
actions are distributed according to the region's distribution settings. When 
an entry is invalid, a `get` causes the cache to retrieve the entry according 
to the steps described in [Entry 
Retrieval](accessing-entries.html#accessing-entries__section_AD6AFD842C144C128FA1C7F0B9283372).
--   **Local destroy**. Destroys the object in the local cache but does not 
distribute the operation.
--   **Local invalidate**. Invalidates the object in the local cache but does 
not distribute the operation.
-    **Note:**
-    Destruction and invalidation cause the same event notification activities 
whether carried out explicitly or through expiration activities.
-
-## <a id="expiration-attributes__section_57F5B32CE9B34F29907E8697F51817F9" 
class="no-quick-link"></a>Region Expiration
-
-Expiration activities in distributed regions can be distributed or performed 
only in the local cache. So one cache could control region expiration for a 
number of caches in the distributed system.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/getting-the-region-size.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/getting-the-region-size.html.md.erb 
b/geode-docs/nativeclient/client-cache/getting-the-region-size.html.md.erb
deleted file mode 100644
index d7d80d8..0000000
--- a/geode-docs/nativeclient/client-cache/getting-the-region-size.html.md.erb
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title:  Getting the Region Size
----
-
-The `Region` API provides a `size` method (`Size` property for .NET) that gets 
the size of a region.
-
-For native client regions, this gives the number of entries in the local 
cache, not on the servers.
-
-See the `Region` API documentation for details.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/initial-capacity.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/initial-capacity.html.md.erb 
b/geode-docs/nativeclient/client-cache/initial-capacity.html.md.erb
deleted file mode 100644
index 18f96d9..0000000
--- a/geode-docs/nativeclient/client-cache/initial-capacity.html.md.erb
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title:  InitialCapacity
----
-
-<a id="initial-capacity__section_AB0163B072DA4DA0B858293CA02E91A1"></a>
-Use this attribute, together with the `LoadFactor` attribute, to set the 
initial parameters on the underlying hashmap that stores region entries. This 
is the number of entries that the region map will be ready to hold when it is 
created.
-
-This declaration sets the region's initial capacity to `10000`:
-
-``` pre
-<region-attributes initial-capacity="10000">
-</region-attributes>
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/invalidating-cached-entries.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/invalidating-cached-entries.html.md.erb 
b/geode-docs/nativeclient/client-cache/invalidating-cached-entries.html.md.erb
deleted file mode 100644
index e13ac0b..0000000
--- 
a/geode-docs/nativeclient/client-cache/invalidating-cached-entries.html.md.erb
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title:  Invalidating or Destroying Cached Entries
----
-
-<a 
id="invalidating-cached-entries__section_9244FABA5204452A8D25D1184310B7EE"></a>
-Invalidating an entry sets the entry's value to `NULL`. Destroying it removes 
the entry from the region altogether. These operations can be carried out in 
the local cache in the following ways:
-
--   Through direct API calls from the client.
--   Through expiration activities based on the entry's statistics and the 
region's attribute settings.
-
-**Note:**
-A user-defined cache writer is called before an operation is completed, and 
can abort an entry destroy operation.
-
-Whether carried out explicitly or through expiration activities, invalidation 
and destruction cause event notification: The `CacheEvent` object has an 
`isExpiration` flag that is set to true for events resulting from expiration 
activities, and set to `false` for all other events.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/invalidating-region.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/invalidating-region.html.md.erb 
b/geode-docs/nativeclient/client-cache/invalidating-region.html.md.erb
deleted file mode 100644
index 0769681..0000000
--- a/geode-docs/nativeclient/client-cache/invalidating-region.html.md.erb
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title:  Invalidating and Destroying Regions
----
-
-Invalidation marks all entries contained in the region as invalid (with null 
values). Destruction removes the region and all of its contents from the cache.
-
-<a id="invalidating-region__section_6F7E304D1D5743F1B53FCBD4F82651D0"></a>
-You can execute these operations explicitly in the local cache in the 
following ways:
-
--   Through direct API calls from the native client.
--   Through expiration activities based on the region's statistics and 
attribute settings.
-
-In either case, you can perform invalidation and destruction as a local or a 
distributed operation.
-
--   A local operation affects the region only in the local cache.
--   A distributed operation works first on the region in the local cache and 
then distributes the operation to all other caches where the region is defined. 
This is the proper choice when the region is no longer needed, or valid, for 
any application in the distributed system.
--   If the region on the server is configured as a partitioned region, it 
cannot be cleared using API calls from the native client.
-
-A user-defined cache writer can abort a region destroy operation. Cache 
writers are synchronous listeners with the ability to abort operations. If a 
cache writer is defined for the region anywhere in the distributed system, it 
is invoked before the region is explicitly destroyed.
-
-Region invalidation and destruction can cause other user-defined application 
plug-ins to be invoked as well. These plug-ins are described in detail in 
[Application Plug-Ins](application-plugins.html#application-plugins).
-
-Whether carried out explicitly or through expiration activities, invalidation 
and destruction cause event notification.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/load-factor.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/load-factor.html.md.erb 
b/geode-docs/nativeclient/client-cache/load-factor.html.md.erb
deleted file mode 100644
index 7643702..0000000
--- a/geode-docs/nativeclient/client-cache/load-factor.html.md.erb
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title:  LoadFactor
----
-
-<a id="load-factor__section_D4102F0D396E4E2DA05654A20FA0723D"></a>
-Use this attribute, together with the `InitialCapacity` attribute, to set the 
initial parameters on the underlying hashmap that stores region entries. When 
the number of entries in the map exceeds the `LoadFactor` times current 
capacity, the capacity is increased and the map is rehashed. You get the best 
performance if you configure a properly sized region at the start and do not 
have to rehash it.
-
-This declaration sets the region's load factor to `0.75` :
-
-``` pre
-<region-attributes load-factor="0.75">
-</region-attributes>
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/lru-entries-limit.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/lru-entries-limit.html.md.erb 
b/geode-docs/nativeclient/client-cache/lru-entries-limit.html.md.erb
deleted file mode 100644
index 8f716e5..0000000
--- a/geode-docs/nativeclient/client-cache/lru-entries-limit.html.md.erb
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title:  LruEntriesLimit
----
-
-<a 
id="concept_75D723D60E044FF9AE97C939699AB10A__section_B0174EA802CB47C9981EF3BDF4B7D169"></a>
-This attribute sets the maximum number of entries to hold in a caching region. 
When the capacity of the caching region is exceeded, a least-recently-used 
(LRU) algorithm is used to evict entries.
-
-**Note:**
-This is a tuning parameter that affects system performance.
-
-When eviction is configured, memory consumption or entry count is monitored 
and, when capacity is reached, Geode makes way for new entries by removing or 
overflowing the stalest LRU entries to disk.
-
-If you use disk data overflow to supplement memory for your data cache, make 
sure you have enough disk space to store the data.
-
-This declaration limits the region to 20,000 entries:
-
-``` pre
-<region-attributes lru-entries-limit="20000"
-     initial-capacity="20000"
-     load-factor="1">
-</region-attributes>
-```
-
-Evicted entries can be destroyed or moved to disk as an extension of the 
cache. See [DiskPolicy](disk-policy.html#disk-policy).
-
-**Note:**
-When `CachingEnabled` is `false`, do not set the `LruEntriesLimit` attribute. 
An `IllegalStateException` is thrown if the attribute is set.
-
-See also [Controlling Cache 
Size](controlling-cache-size.html#controlling-cache-size).
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/managing-lifetime-cached-object.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/managing-lifetime-cached-object.html.md.erb
 
b/geode-docs/nativeclient/client-cache/managing-lifetime-cached-object.html.md.erb
deleted file mode 100644
index 0eb18d4..0000000
--- 
a/geode-docs/nativeclient/client-cache/managing-lifetime-cached-object.html.md.erb
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title:  Managing the Lifetime of a Cached Object
----
-
-All cacheable objects derive from `SharedBase` , which provides reference 
counting. Cacheable objects are referenced using `SharedPtr` types.
-
-<a 
id="managing-lifetime-cached-object__section_5F8E6FE4F9AB4C658516DB0D31DD4FF8"></a>
-When `SharedPtr` retrieves a cached object, the object remains alive as long 
as that pointer or the cache itself references the object.
-
-A native client may have many pointers that reference an object. Regardless of 
how many pointers to the object are deleted, the object remains alive until the 
last remaining pointer is deleted. At that point the object is deleted.
-
-This is a very simple example:
-
-``` pre
-CacheableStringPtr p = CacheableString::create("string");
-region.put("key", p) ;
-```
-
-In the example:
-
--   The act of object creation allocates memory and initializes the object.
--   When you assign the object to a `SharedPtr` , you relinquish control of 
the lifetime of that object to the reference counting mechanism for the cache.
--   The put operation does not actually copy the object into the cache. 
Rather, it copies a `SharedPtr` into the cache's hashmap. Consequently, the 
object remains alive in the cache when the original `SharedPtr` goes away.
-
-The client can make use of an object after you have initialized the object. 
For example, another `SharedPtr` might issue a `get` to retrieve the object 
from the cache:
-
-``` pre
-CacheableStringPtr p2 = region.get("key");
-```
-
-Because `p` (the original `SharedPtr`) and `p2` point to the same object in 
memory, it is possible under some circumstances for multiple `SharedPtr` types 
to work on the same object in data storage.
-
-**Note:**
-Once you have put an object into the cache, do not delete it explicitly. 
Attempting to do so can produce undesirable results.
-
-## <a 
id="managing-lifetime-cached-object__section_8753DE6DF3864BEC806D39F623CBE3E0" 
class="no-quick-link"></a>Changed Objects
-
-If an object update is received, the cache no longer holds the same object. 
Rather, it holds a completely different instance of the object. The client does 
not see the updates until it calls a `get` to fetch the object again from the 
local cache, or (in a cache plug-in) calls `EntryEvent::getNewValue`.
-
-For more about plug-ins, see [Application 
Plug-Ins](application-plugins.html#application-plugins).
-
-## <a 
id="managing-lifetime-cached-object__section_065526A7FFBB464591A5E119EB8D6CA6" 
class="no-quick-link"></a>Object Expiration
-
-When a cache automatically deletes an object as a result of an expiration 
action, the reference counting pointers protect the client from situations that 
might otherwise result if the cache actually freed the object's memory. 
Instead, the client disconnects the object from the cache by deleting the 
cache's `SharedPtr` reference, while leaving untouched any client threads with 
a `SharedPtr` to that object.
-
-## <a 
id="managing-lifetime-cached-object__section_6D700999EE534BD7999D5B428301F5A6" 
class="no-quick-link"></a>Object Lifetime Across the Distributed Cache
-
-An object remains alive until every copy of the object is gone. In distributed 
regions, expiration activities can be local or distributed, depending on a 
region's distribution settings. One cache could control the expiration of all 
copies of an object in all the caches in the distributed system. Alternatively, 
each cache could control the expiration of its own local copy of the object. If 
the configuration gives each cache local control, and the expiration parameters 
are set to different lengths of time in different caches, some copies of an 
object may still exist after it has disappeared in other caches. See 
[Expiration Attributes](expiration-attributes.html#expiration-attributes) for 
more information.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/notification-for-operations.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/notification-for-operations.html.md.erb 
b/geode-docs/nativeclient/client-cache/notification-for-operations.html.md.erb
deleted file mode 100644
index 0abfdcb..0000000
--- 
a/geode-docs/nativeclient/client-cache/notification-for-operations.html.md.erb
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title:  Notification for Operations
----
-
-<a 
id="notification-for-operations__section_53F43C51118C4087915CB954CA3439E0"></a>
-Listeners are invoked for client-initiated operations only after the client 
operation succeeds on the server. Listener invocation on the client indicates 
that the server has the same data as the client.
-
-If a client operation fails on the server, the operation is rolled back, 
assuming that no other thread has modified the data in the intervening period. 
Rollback may not be possible in cases where the entry has been evicted by LRU 
or expiration during this period. Thus when an exception is received from the 
server for an operation, local changes may not have been rolled back
-
-## <a 
id="notification-for-operations__section_48240559E20D4FAF8FDEC8D62C098357" 
class="no-quick-link"></a>Event Notification Sequence
-
-Events received on the clients that originated on the server invoke the 
subscription for the event as seen by the server. Events originating on the 
client invoke the subscription as seen by the client.
-
-For example, a client that receives a `create` and an `update` from the server 
fires a `create` event and an `update` event because that is how the server saw 
it. A cacheless client that does two consecutive put operations has two 
`afterCreate` events invoked on the originating client because the client does 
not have any history about the first put , since it is cacheless.
-
-For the same sequence, the server sees an `afterCreate` and an `afterUpdate` 
event, and a remote client receiving the event sees an `afterCreate` followed 
by an `afterUpdate` event. A client that caches locally sees an `afterCreate` 
and an `afterUpdate` for the same scenario (as will the server and remote 
clients).

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/overview-client-cache.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/overview-client-cache.html.md.erb 
b/geode-docs/nativeclient/client-cache/overview-client-cache.html.md.erb
deleted file mode 100644
index 30689db..0000000
--- a/geode-docs/nativeclient/client-cache/overview-client-cache.html.md.erb
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title:  About the Native Client Cache
----
-
-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.
-
-The `Cache` instance allows your process to set general parameters for 
communication between a cache and other caches in the distributed system, and 
to create and access any region in the cache.
-
-Regions are created from the `Cache` instance. Regions provide the entry point 
to the interfaces for instances of `Region` and `RegionEntry`.
-
-## <a id="native-client-cache__section_A0F2E9EF30324736BD0D5F92FE3D1BD7" 
class="no-quick-link"></a>Main Features and Functionality
-
-The native client cache provides the following features and functionality.
-
--   Local and distributed data caching for fast access.
--   Data distribution between applications on the same or different platforms.
--   Local and remote data loading through application plug-ins.
--   Application plug-ins for synchronous and asynchronous handling of data 
events.
--   Automated and application-specific data eviction for freeing up space in 
the cache, including optional overflow to disk.
--   System message logging, and statistics gathering and archiving.
-
-For more information specific to your client programming language, see the 
online API documentation and [Working with the C++ 
API](../cpp-caching-api/cpp-caching-api.html#concept_CEC658A999414AC3A494578C214BF64E)
 and [Working with the .NET Caching 
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/persistence-manager.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/persistence-manager.html.md.erb 
b/geode-docs/nativeclient/client-cache/persistence-manager.html.md.erb
deleted file mode 100644
index 1d71808..0000000
--- a/geode-docs/nativeclient/client-cache/persistence-manager.html.md.erb
+++ /dev/null
@@ -1,224 +0,0 @@
----
-title:  PersistenceManager
----
-
-For each region, if the disk-policy attribute is set to overflows, a 
persistence-manager plug-in must perform cache-to-disk and disk-to-cache 
operations. See [Application 
Plug-Ins](application-plugins.html#application-plugins).
-
-Persistence manager declaration:
-
-``` pre
-<region-attributes lru-entries-limit="nnnnn"
-        disk-policy="overflows">
-    <persistence-manager library-name="libraryName"
-            library-function-name="functionName">
-        <properties>
-            <property name="propertyName" value="propertyValue" />
-        </properties>
-    </persistence-manager>
-</region-attributes>
-```
-
-The optional properties set parameters for the plug-in.
-
-
-## <a id="persistence-manager__section_9FC7089FDF8044868F17A2659397402A" 
class="no-quick-link"></a>Using SQLite as a Persistence Manager
-
-The Geode native client distribution includes a persistence manager that uses 
the open-source SQLite library.
-
-SQLite is a software library that implements a self-contained transactional 
SQL database. SQLite does not require its own server or separate configuration, 
and the source code for SQLite is in the public domain. For more information on 
SQLite, see [http://www.sqlite.org](http://www.sqlite.org).
-
-Each SQLite persistence manager persists its region data in a SQLite database 
that is stored in disk files. In a given native client application process, 
each region must have a unique persistence (overflow) directory.
-
-<a id="persistence-manager__fig_6A0C9F1A29134ACBA0FDD8236CD836B6"></a>
-<span class="figtitleprefix">Figure: </span>SQLite Database Persistence 
Manager Directory Structure
-
-<img src="../../images/SQLite_Persistence_Mgr.png" 
id="persistence-manager__image_BD1AF915E09548D68D9307E2F52737F9" class="image" 
/>
-
-## <a id="persistence-manager__section_3C6991A39C5F4FB8A945EF15FB089287" 
class="no-quick-link"></a>SQLite Persistence Manager Region Attributes
-
-The following table describes the region attributes that can be configured for 
the SQLite persistence manager.
-
-| Property             | Description                                           
                                                                                
                                                                                
                                                                                
     | Default Setting                                                          
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
             |
-|----------------------|------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
-| PersistenceDirectory | Directory where each region's database files are 
stored. This setting must be different for each region including regions in 
different processes. This directory is created by the persistence manager. The 
persistence manager fails to initialize if this directory already exists or 
cannot be created. | Default is to create a subdirectory named 
GemFireRegionData in the directory where the process using the region was 
started.                                                                        
                                                                                
                                                                                
                                                                                
                                                                                
                                                  |
-| PageSize             | Maximum page size of the SQLite database. SQLite can 
limit the size of a database file to prevent the database file from growing too 
large and consuming too much disk space.                                        
                                                                                
      | Ordinarily, if no value is explicitly provided, SQLite creates a 
database with the page size set to SQLITE\_DEFAULT\_PAGE\_SIZE (default is 
1024). However, based on certain device characteristics (for example, 
sector-size and atomic write() support) SQLite may choose a larger value. 
PageSize specifies the maximum value that SQLite will be able to choose on its 
own. See <a 
href="http://www.sqlite.org/compile.html#default_page_size";>http://www.sqlite.org/compile.html#default_page_size</a>.
 for more details on SQLITE\_DEFAULT\_PAGE\_SIZE. |
-| MaxPageCount         | Maximum number of pages in one database file.         
                                                                                
                                                                                
                                                                                
     | SQLite default, which is 1073741823.                                     
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
                                                                                
             |
-
-## <a id="persistence-manager__section_A9583FBEB5D74B92AD61CB6158AE2B4C" 
class="no-quick-link"></a>Configuring the SQLite Persistence Manager Plug-In 
for C++ Applications
-
-To load the SQLite persistence manager plug-in for C++ applications, you can 
configure it either in your client's `cache.xml` or programmatically using the 
native client C++ API.
-
-The following is an example of how to specify the following region attributes 
in your client's cache.xml:
-
-``` pre
-<region-attributes>
-   <persistence-manager library-name="libSqLiteImpl.so" 
library-function-name="createSqLiteInstance">
-      <properties>
-         <property name="PersistenceDirectory" value="/xyz"/>
-         <property name="PageSize" value="65536"/>
-         <property name="MaxPageCount" value="1073741823"/>
-      </properties>
-   </persistence-manager>
-</region-attributes>
-```
-
-## C++ API Example
-
-To use the native client C++ API, set SQLite persistence manager attributes 
programmatically as follows:
-
-``` pre
-PropertiesPtr sqliteProperties = Properties::create();
-sqliteProperties->insert("MaxPagecount", "5");
-sqliteProperties->insert("PageSize", "1024");
-sqliteProperties->insert("PersistenceDirectory", "SqLite-Test779");
-regionFactory->setPersistenceManager("SqLiteImpl","createSqLiteInstance",
-          sqliteProperties);
-```
-
-## <a id="persistence-manager__section_7410F68E0BB144A584A9AFE7E8CDBE22" 
class="no-quick-link"></a>Configuring the SQLite Persistence Manager Plug-In 
for .NET Applications
-
-To load the SQLite persistence manager plug-in for .NET applications, you can 
configure it either in your client's cache.xml or programmatically using the 
.NET API:
-
-``` pre
-<persistence-manager library-name="Gemstone.Gemfire.Plugins.SqLite" 
-   
library-function-name="GemStone.GemFire.Plugins.SqLite.SqLiteImpl&lt;System.Object,
 System.Object&gt;.Create"> 
-    <properties>
-       <property name="PersistenceDirectory" value="SqLite"/>
-       <property name="MaxPageCount" value="1073741823"/>
-       <property name="PageSize" value="65536"/>
-    </properties>
-</persistence-manager>
-```
-
-## .NET API Example
-
-To use the native client .NET API, set the SQLite persistence manager 
attributes programmatically as follows:
-
-``` pre
-Properties<string, string> sqliteProperties = new Properties<string, string>();
-sqliteProperties.Insert("PageSize", "65536");
-sqliteProperties.Insert("MaxFileSize", "51200000");
-sqliteProperties.Insert("PersistenceDirectory", SqLiteDir);
-rf.SetPersistenceManager("Gemstone.Gemfire.Plugins.SqLite", 
-"Gemstone.Gemfire.Plugins.SqLiteSqLiteImpl<System.Object,System.Object>.Create",
-sqliteProperties);
-```
-
-You can also use and configure the C++ SQLite persistence manager library from 
your .NET application as follows:
-
-``` pre
-rf.SetPersistenceManager("SqliteImpl", "createSqLiteInstance", 
sqliteProperties);
-```
-
-## <a id="persistence-manager__section_9D038C438E01415EA4D32000D5CB5596" 
class="no-quick-link"></a>Implementing a PersistenceManager with the 
IPersistenceManager Interface
-
-When developing .NET managed applications, you can use the IPersistenceManager 
managed interface to implement your own persistence manager. The following code 
sample provides the IPersistenceManager interface:
-
-``` pre
-/// <summary> 
-/// IPersistenceManager interface for persistence and overflow. 
-/// This class abstracts the disk-related operations in case of persistence or 
overflow to disk. 
-/// A specific disk storage implementation will implement all the methods 
described here. 
-/// </summary> 
-generic<class TKey, class TValue> 
-public interface class IPersistenceManager 
- { 
-   public: 
-   /// <summary> 
-   /// Called after an implementation object is created. Initializes all the 
implementation specific environments needed. 
-   /// </summary> 
-   /// <param name="region"> 
-   /// Region for which this PersistenceManager is initialized. 
-   /// </param> 
-   /// <param name="diskProperties"> 
-   /// Configuration Properties used by PersistenceManager implementation. 
-   /// </param> 
-   void Init(IRegion<TKey, TValue>^ region, Properties<String^, String^>^ 
diskProperties); 
-   
-   /// <summary> 
-   /// Writes a key, value pair of region to the disk. The actual file or 
database related write operations should be implemented in this method. 
-   /// </summary> 
-   /// <param name="key"> 
-   /// the key to write. 
-   /// </param> 
-   /// <param name="value"> 
-   /// the value to write. 
-   /// </param> 
-   void Write(TKey key, TValue value); 
-
-   /// <summary> 
-   /// This method is not used. 
-   /// </summary> 
-   bool WriteAll(); 
-
-   /// <summary> 
-   /// Reads the value for the key from the disk. 
-   /// </summary> 
-   /// <param name="key"> 
-   /// key for which the value has to be read. 
-   /// </param> 
-   TValue Read(TKey key); 
-
-   /// <summary> 
-   /// This method is not used. 
-   /// </summary> 
-   bool ReadAll(); 
-
-   /// <summary> 
-   /// Destroys the entry specified by the key in the argument. 
-   /// </summary> 
-   /// <param name="key"> 
-   /// key of the entry which is being destroyed. 
-   /// </param>
-   void Destroy(TKey key); 
-
-   /// <summary> 
-   /// Closes the persistence manager instance. 
-   /// </summary> 
-   void Close(); 
-}
-```
-
-The following is a sample interface implementation:
-
-``` pre
-class MyPersistenceManager<TKey, TValue> : IPersistenceManager<TKey, TValue> 
-   { 
-      #region IPersistenceManager<TKey,TValue> Members
-      public void Close() 
-      { 
-         throw new NotImplementedException(); 
-      } 
-
-      public void Destroy(TKey key) 
-      { 
-         throw new NotImplementedException(); 
-      } 
-
-      public void Init(IRegion<TKey, TValue> region, Properties<string, 
string> disk Properties) 
-      { 
-         throw new NotImplementedException(); 
-      } 
-
-      public TValue Read(TKey key) 
-      { 
-         throw new NotImplementedException(); 
-      } 
-
-      public void Write(TKey key, TValue value) 
-      { 
-         throw new NotImplementedException(); 
-      } 
-
-      public bool ReadAll() 
-      { 
-         throw new NotImplementedException(); 
-      } 
-
-      public bool WriteAll() 
-      {
-         throw new NotImplementedException(); 
-      } 
-      #endregion 
-   }
-```

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/programmatic-region-creation.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/programmatic-region-creation.html.md.erb 
b/geode-docs/nativeclient/client-cache/programmatic-region-creation.html.md.erb
deleted file mode 100644
index f3f8757..0000000
--- 
a/geode-docs/nativeclient/client-cache/programmatic-region-creation.html.md.erb
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title:  Programmatic Region Creation
----
-
-You create regions programmatically with the `regionFactory` class.
-
-**Note:**
-Before creating a region, specify region attributes. See [Region 
Attributes](region-attributes.html#region-attributes).
-
-Create your regions using the `regionFactory` class.
-
-**C++ RegionFactory Example**
-
-``` pre
-RegionFactoryPtr regionFactory =
-    cachePtr->createRegionFactory(CACHING_PROXY);
-RegionPtr regPtr0 = regionFactory->setLruEntriesLimit(20000)
-        ->create("exampleRegion0");
-    
-```
-
-**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.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/region-access.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/region-access.html.md.erb 
b/geode-docs/nativeclient/client-cache/region-access.html.md.erb
deleted file mode 100644
index efb6fee..0000000
--- a/geode-docs/nativeclient/client-cache/region-access.html.md.erb
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title:  Region Access
----
-
-You can use `Cache::getRegion` to retrieve a reference to a specified region.
-
-`RegionPtr` returns `NULL` if the region is not already present in the 
application's cache. A server region must already exist.
-
-A region name *cannot* contain these characters:
-
--   &lt;
--   &gt;
--   :
--   "
--   /
--   \\
--   |
--   ?
--   \*
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb 
b/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb
deleted file mode 100644
index f667d30..0000000
--- a/geode-docs/nativeclient/client-cache/region-attributes-desc.html.md.erb
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title:  Mutable and Immutable Region Attributes
----
-
-Attributes that are immutable (fixed) after region creation govern storage 
location, data distribution, statistics, application plug-ins, and the 
configuration and management of the region's data hashmap.
-
-This table lists the immutable attributes and their default settings.
-
-<a id="region-attributes-desc__table_B1CC036A7929449A8CD06E56678A6CB2"></a>
-
-| Immutable Region Attribute                                                   
                                                             | Default Setting |
-|-------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
-| See [CachingEnabled](caching-enabled.html#caching-enabled)                   
                                     | true            |
-| See [InitialCapacity](initial-capacity.html#initial-capacity)                
                                     | 16 (entries)    |
-| See [LoadFactor](load-factor.html#load-factor)                               
                                     | 0.75            |
-| See [ConcurrencyLevel](concurrency-level.html#concurrency-level)             
                                     | 16              |
-| See [DiskPolicy](disk-policy.html#disk-policy)                               
                                     |                 |
-| See [PersistenceManager](persistence-manager.html#persistence-manager)       
                                     | NULL            |
-| PartitionResolver. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins). |                 |
-
-
-Mutable region attributes identify expiration and cache listener, cache writer 
and cache loader actions that are run from the defining client. The next table 
lists the mutable attributes that generally can be modified after region 
creation by using the `AttributesMutator` for the region.
-
-<a id="region-attributes-desc__table_98120276A645432A840F991C18039621"></a>
-
-| Mutable Region Attribute                                                     
                                                            | Default Setting |
-|------------------------------------------------------------------------------------------------------------------------------------------|-----------------|
-| Expiration attributes. See [Specifying Expiration 
Attributes](expiration-attributes.html#expiration-attributes). | no expiration  
 |
-| See 
[LruEntriesLimit](lru-entries-limit.html#concept_75D723D60E044FF9AE97C939699AB10A).
                          | 0 (no limit)    |
-| CacheLoader. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).      |               
  |
-| CacheWriter. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).      |               
  |
-| CacheListener. See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins).    |                 
|
-
-
-See [Specifying Application Plug-In 
Attributes](application-plugins.html#application-plugins) for information about 
using `AttributesMutator` with cache listeners, cache loaders, and cache 
writers.
-
-The remainder of this section examines these attributes in detail. Throughout 
the descriptions, `cache.xml` file snippets show how each attribute can be set 
declaratively.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/region-attributes.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/region-attributes.html.md.erb 
b/geode-docs/nativeclient/client-cache/region-attributes.html.md.erb
deleted file mode 100644
index 784e4c6..0000000
--- a/geode-docs/nativeclient/client-cache/region-attributes.html.md.erb
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title:  Region Attributes
----
-
-Region attributes govern the automated management of a region and its entries.
-
-Region attribute settings determine where the data resides, how the region is 
managed in memory, and the automatic loading, distribution, and expiration of 
region entries.
-
--   **[Specifying Region 
Attributes](../../nativeclient/client-cache/specify-region-attributes.html)**
-
--   
**[RegionShortcuts](../../nativeclient/client-cache/region-shortcuts.html)**
-
--   **[Mutable and Immutable Region 
Attributes](../../nativeclient/client-cache/region-attributes-desc.html)**
-
--   **[CachingEnabled](../../nativeclient/client-cache/caching-enabled.html)**
-
--   
**[InitialCapacity](../../nativeclient/client-cache/initial-capacity.html)**
-
--   **[LoadFactor](../../nativeclient/client-cache/load-factor.html)**
-
--   
**[ConcurrencyLevel](../../nativeclient/client-cache/concurrency-level.html)**
-
--   
**[ConcurrencyChecksEnabled](../../nativeclient/client-cache/concurrency-checks-enabled.html)**
-
--   
**[LruEntriesLimit](../../nativeclient/client-cache/lru-entries-limit.html)**
-
--   **[DiskPolicy](../../nativeclient/client-cache/disk-policy.html)**
-
--   
**[PersistenceManager](../../nativeclient/client-cache/persistence-manager.html)**
-
--   **[Specifying Application Plug-In 
Attributes](../../nativeclient/client-cache/application-plugins.html)**
-
--   **[Specifying Expiration 
Attributes](../../nativeclient/client-cache/expiration-attributes.html)**
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/region-shortcuts.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/region-shortcuts.html.md.erb 
b/geode-docs/nativeclient/client-cache/region-shortcuts.html.md.erb
deleted file mode 100644
index 72441e5..0000000
--- a/geode-docs/nativeclient/client-cache/region-shortcuts.html.md.erb
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title:  RegionShortcuts
----
-
-<a id="region-shortcuts__section_62D2AB580EDB4165970E4FC42A35C80B"></a>
-Geode provides a number of predefined, shortcut region attributes settings for 
your use, in `RegionShortcut`.
-
-Shortcut attributes are a convenience only. They are named attributes that 
Geode has already stored for you. You can override their settings by storing 
new attributes with the same `id` as the predefined attributes.
-
-You can also create custom region attributes and store them with an identifier 
for later retrieval. Both types of stored attributes are referred to as named 
region attributes. You can create and store your attribute settings in the 
`cache.xml` file and through the API.
-
-Retrieve named attributes by providing the ID to the region creation. This 
example uses the shortcut `CACHING_PROXY` attributes to create a region:
-
-``` pre
-<region name="testRegion" refid="CACHING_PROXY"/>
-```
-
-You can modify named attributes as needed. For example, this adds a cache 
listener to the region:
-
-``` pre
-<region name="testRegion" refid="CACHING_PROXY">
-    <region-attributes>
-        <cache-listener library-name="myAppLib"
-            library-function-name ="myCacheListener" />
-    </region-attributes>
-</region>
-```
-
-In this example, the modified region shortcut is saved to the cache using the 
region attribute id, for retrieval and use by a second region:
-
-``` pre
-<region name="testRegion" refid="CACHING_PROXY">
-    <region-attributes id="Caching_Proxy_With_Listener">
-        <cache-listener library-name="myAppLib"
-            library-function-name ="myCacheListener" />
-    </region-attributes>
-</region>
-<region name="newTestRegion" refid="Caching_Proxy_With_Listener"/>
-```
-
-## <a id="region-shortcuts__section_49150358B8F443E8AF027E4E920E820A" 
class="no-quick-link"></a>Shortcut Attribute Options
-
-You can select the most common region attributes settings from 
`RegionShortcut`, the predefined named region attributes.
-
-This section provides an overview of the options available in the region 
shortcut settings.
-
-**Note:**
-For complete listings and descriptions, including information on the 
underlying `RegionAttributes` settings for each shortcut, see the online 
documentation for `RegionShortcut`.
-
-These are the options available in `RegionShortcut`.
-
-**Communication with Servers and Data Storage**
-
--   `PROXY` does not store data in the client cache, but connects the region 
to the servers for data requests and updates, interest registrations, and so on.
--   `CACHING_PROXY` stores data in the client cache and connects the region to 
the servers for data requests and updates, interest registrations, and so on.
--   `LOCAL` stores data in the client cache and does not connect the region to 
the servers. This is a client-side-only region.
-
-**Data Eviction**
-
-For the non-`PROXY` regions--the regions that store data in the client 
cache--you can add data eviction:
-
--   `ENTRY_LRU` causes least recently used data to be evicted from memory when 
the region reaches the entry count limit.
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/regions.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/regions.html.md.erb 
b/geode-docs/nativeclient/client-cache/regions.html.md.erb
deleted file mode 100644
index a64484f..0000000
--- a/geode-docs/nativeclient/client-cache/regions.html.md.erb
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title:  Regions
----
-
-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.
-
-<a id="regions__section_1BE4ABB76537488C966E452C2D89478F"></a>
-The region is the core building block of the Geode distributed system. All 
cached data is organized into data regions and you do all of your data puts, 
gets, and querying activities against them.
-
-A distributed region can be either non-partitioned or a partitioned region. 
See [Data Regions](../../basic_config/data_regions/chapter_overview.html) for 
detailed descriptions of both non-partitioned and partitioned regions. Region 
creation is subject to attribute consistency checks. The requirements for 
consistency between attributes are detailed both in the online API 
documentation and throughout the discussion of [Region 
Attributes](region-attributes.html#region-attributes).
-
--   **[Declarative Region 
Creation](../../nativeclient/client-cache/declarative-region-creation.html)**
-
-    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.
-
--   **[Programmatic Region 
Creation](../../nativeclient/client-cache/programmatic-region-creation.html)**
-
-    You create regions programmatically with the `regionFactory` class.
-
--   **[Invalidating and Destroying 
Regions](../../nativeclient/client-cache/invalidating-region.html)**
-
-    Invalidation marks all entries contained in the region as invalid (with 
null values). Destruction removes the region and all of its contents from the 
cache.
-
--   **[Region Access](../../nativeclient/client-cache/region-access.html)**
-
-    You can use `Cache::getRegion` to retrieve a reference to a specified 
region.
-
--   **[Getting the Region 
Size](../../nativeclient/client-cache/getting-the-region-size.html)**
-
-    The `Region` API provides a `size` method (`Size` property for .NET) that 
gets the size of a region.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/registering-interest-for-entries.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/registering-interest-for-entries.html.md.erb
 
b/geode-docs/nativeclient/client-cache/registering-interest-for-entries.html.md.erb
deleted file mode 100644
index aac6fae..0000000
--- 
a/geode-docs/nativeclient/client-cache/registering-interest-for-entries.html.md.erb
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title:  Registering Interest for Entries
----
-
-For native client regions, you can programmatically register interest in entry 
keys stored on a cache server region. A client region receives update 
notifications from the cache server for the keys of interest.
-
-You can register interest for specific entry keys or for all keys. Regular 
expressions can be used to register interest for keys whose strings match the 
expression. You can also unregister interest for specific keys, groups of keys 
based on regular expressions, or for all keys.
-
-**Note:** Interest registration and unregistration are symmetrical operations. 
Consequently, you cannot register interest in all keys and then unregister 
interest in a specific set of keys. Also, if you first register interest in 
specific keys with `registerKeys`, then call `registerAllKeys`, you must call 
`unregisterAllKeys` before specifying interest in specific keys again.
-
-
-## <a 
id="registering-interest-for-entries__section_C9A3D7F193B24ACD83B2D67813E596A0" 
class="no-quick-link"></a>Client API for Registering Interest
-
-You register client interest through the C++ or NET API. The C++ API provides 
the `registerKeys`, `registerAllKeys`, and `registerRegex` methods, with 
corresponding unregistration accomplished using the `unregisterKeys`, 
`unregisterAllKeys`, and `unregisterRegex` methods. The .NET API provides the 
`RegisterKeys`, `RegisterAllKeys`, and `RegisterRegex` methods, with 
corresponding unregistration accomplished using the `UnregisterKeys`, 
`UnregisterAllKeys`, and `UnregisterRegex` methods.
-
-The `registerKeys`, `registerRegex` and `registerAllKeys` methods have the 
option to populate the cache with the registration results from the server. The 
`registerRegex` and `registerAllKeys` methods can also optionally return the 
current list of keys registered on the server.
-
-## <a 
id="registering-interest-for-entries__section_C1A3F89EE73448D7AFF2076F41848F55" 
class="no-quick-link"></a>Setting Up Client Notification
-
-In addition to the programmatic function calls, to register interest for a 
server region and receive updated entries you need to configure the region with 
the `PROXY` or `CACHING_PROXY RegionShortcut` setting. The region's pool should 
have `subscription-enabled=true` set either in the client XML or 
programmatically via a `CacheFactory::setSubscriptionEnabled(true)` API call. 
Otherwise, when you register interest, you will get an 
`UnsupportedOperationException`.
-
-``` pre
-<region name = "listenerWriterLoader" refid="CACHING_PROXY">
-   ... 
-```
-
-Both native clients and Java clients that have subscriptions enabled track and 
drop (ignore) any duplicate notifications received. To reduce resource usage, a 
client expires tracked sources for which new notifications have not been 
received for a configurable amount of time.
-
-**Notification Sequence**
-
-Notifications invoke `CacheListeners` of cacheless clients in all cases for 
keys that have been registered on the server. Similarly, invalidates received 
from the server invoke `CacheListeners` of cacheless clients.
-
-If you register to receive notifications, listener callbacks are invoked 
irrespective of whether the key is in the client cache when a `destroy` or 
`invalidate` event is received.
-
-## <a 
id="registering-interest-for-entries__section_8772147940754C2D9688C789EB2F2AA6" 
class="no-quick-link"></a>Registering Interest for Specific Keys
-
-You register and unregister interest for specific keys through the 
`registerKeys` and `unregisterKeys` functions. You register interest in a key 
or set of keys by specifying the key name using the programmatic syntax shown 
in the following example:
-
-``` pre
-keys0.push_back(keyPtr1);
-keys1.push_back(keyPtr3);
-regPtr0->registerKeys(keys0);
-regPtr1->registerKeys(keys1); 
-```
-
-The programmatic code snippet in the next example shows how to unregister 
interest in specific keys:
-
-``` pre
-regPtr0->unregisterKeys(keys0);
-regPtr1->unregisterKeys(keys1);
-```
-
-## <a 
id="registering-interest-for-entries__section_EA4525CCDC474DD495410E948EAF566C" 
class="no-quick-link"></a>Registering Interest for All Keys
-
-If the client registers interest in all keys, the server provides 
notifications for all updates to all keys in the region. The next example shows 
how to register interest in all keys:
-
-``` pre
-regPtr0->registerAllKeys();
-regPtr1->registerAllKeys();
-```
-
-The following example shows a code sample for unregistering interest in all 
keys.
-
-``` pre
-regPtr0->unregisterAllKeys();
-regPtr1->unregisterAllKeys();
-```
-
-## <a 
id="registering-interest-for-entries__section_BD50B80FCE9F429C8F6A9FEA818D5A91" 
class="no-quick-link"></a>Registering Interest Using Regular Expressions
-
-The `registerRegex` function registers interest in a regular expression 
pattern. The server automatically sends the client changes for entries whose 
keys match the specified pattern.
-
-*Keys must be strings in order to register interest using regular expressions.*
-
-The following example shows interest registration for all keys whose first 
four characters are `Key-`, followed by any string of characters. The 
characters `.*` represent a wildcard that matches any string.
-
-``` pre
-regPtr1->registerRegex("Key-.*");
-```
-
-To unregister interest using regular expressions, you use the 
`unregisterRegex` function. The next example shows how to unregister interest 
in all keys whose first four characters are `Key-`, followed by any string 
(represented by the `.*` wildcard).
-
-``` pre
-regPtr1->unregisterRegex("Key-.*");
-```
-
-## <a 
id="registering-interest-for-entries__section_2D71A423B185493489129AAC30DC6733" 
class="no-quick-link"></a>Register Interest Scenario
-
-In this register interest scenario, a cache listener is used with a cacheless 
region that has `subscription-enabled` set to `true`. The client region is 
configured with caching disabled; client notification is enabled; and a cache 
listener is established. The client has not registered interest in any keys.
-
-When a value changes in another client, it sends the event to the server. The 
server will not send the event to the cacheless client, even though 
`client-notification` is set to `true`.
-
-To activate the cache listener so the cacheless region receives updates, the 
client should explicitly register interest in some or all keys by using one of 
the API calls for registering interest. This way, the client receives all 
events for the keys to which it has registered interest. This applies to 
Java-based clients as well as native clients.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/requirements-for-distrib.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/requirements-for-distrib.html.md.erb 
b/geode-docs/nativeclient/client-cache/requirements-for-distrib.html.md.erb
deleted file mode 100644
index a69ab3b..0000000
--- a/geode-docs/nativeclient/client-cache/requirements-for-distrib.html.md.erb
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title:  Entry Distribution Requirements
----
-
-Entry data distributed among members of the distributed system must be 
serializable. Entry keys and values are serialized for distribution.
-
-If a native client defines a region, it must register any serializable types 
for all classes of objects stored in the region. This includes entries that the 
application gets or puts, as well as entries that are pushed to the client's 
cache automatically through distribution. The types must be registered before 
the native client connects to the distributed system.
-
-See [Serializing 
Data](../cpp-caching-api/serialization_overview.html#concept_2A8DC49D93394392BA34B17AA3452B14)
 for more information about these requirements.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/specify-region-attributes.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/specify-region-attributes.html.md.erb 
b/geode-docs/nativeclient/client-cache/specify-region-attributes.html.md.erb
deleted file mode 100644
index 08ea595..0000000
--- a/geode-docs/nativeclient/client-cache/specify-region-attributes.html.md.erb
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title:  Specifying Region Attributes
----
-
-Region attributes govern the automated management of a region and its entries.
-
-Specify region attributes before creating the region. You can do this either 
through the declarative XML file or through the API. The API includes classes 
for defining a region's attributes before creation and for modifying some of 
them after creation. For details, see the online API documentation for 
`RegionShortcut`, `RegionAttributes`, `AttributesFactory`, and 
`AttributesMutator`.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/troubleshooting.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/troubleshooting.html.md.erb 
b/geode-docs/nativeclient/client-cache/troubleshooting.html.md.erb
deleted file mode 100644
index 8d7dacb..0000000
--- a/geode-docs/nativeclient/client-cache/troubleshooting.html.md.erb
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title:  Troubleshooting
----
-
-This section provides troubleshooting information for the native client.
-
-## <a id="troubleshooting__section_32E817A073B8408F8FEDB5599C5CCEF6" 
class="no-quick-link"></a>Cannot Acquire Windows Performance Data
-
-When you attempt to run performance measurements for the native client on 
Windows, you may encounter the following error message in the run logs:
-
-``` pre
-Can't get Windows performance data. RegQueryValueEx returned 5
-```
-
-This can occur because incorrect information is returned when a Win32 
application calls the ANSI version of `RegQueryValueEx` Win32 API with 
`HKEY_PERFORMANCE_DATA`. This error is described in Microsoft KB article ID 
226371 at 
[http://support.microsoft.com/kb/226371/en-us](http://support.microsoft.com/kb/226371/en-us).
-To successfully acquire Windows performance data, you need to verify that you 
have the proper registry key access permissions in the system registry. In 
particular, make sure that `Perflib` in the following registry path is readable 
(`KEY_READ` access) by the Geode process:
-
-``` pre
-HKEY_LOCAL_MACHINE\
-    SOFTWARE\
-    Microsoft\
-    Windows NT\
-    CurrentVersion\
-    Perflib
-```
-
-An example of reasonable security on the performance data would be to grant 
administrators `KEY_ALL_ACCESS` and interactive users `KEY_READ` access. This 
particular configuration prevents non-administrator remote users from querying 
performance data.
-
-See 
[http://support.microsoft.com/kb/310426](http://support.microsoft.com/kb/310426)
 and 
[http://support.microsoft.com/kb/146906](http://support.microsoft.com/kb/146906)
 for instructions about how to ensure that Geode processes have access to the 
registry keys associated with performance.
-
-## <a id="troubleshooting__section_65EC3B1EAC55421BB734E72E7BFEBFFC" 
class="no-quick-link"></a>Generating a Process Memory Dump Image for Fatal 
Errors
-
-You can generate a process memory dump image (core files in Unix systems and 
minidumps in Windows). The image is produced when a fatal error occurs that 
normally terminates the program.
-
-When the system property `crash-dump-enabled` is set to `true`, a dump image 
is generated (the default is `true`). The dump file is generated in the same 
location as the `log-file` directory, and has the same prefix as the log file. 
The name is `<prefix>-<time>.core.<pid>` in Unix, and 
`<prefix>-<time>-<pid>.dmp` in Windows).
-
-Unix systems generate core files automatically for such errors, but this 
option is useful for providing a custom location and name, as well as for 
systems where core dump generation is disabled. For Unix, when system core dump 
generation is turned on (`ulimit -c`) this property can be set to `false`.
-
-For .NET clients, when this property is set then `AccessViolation` exceptions 
are trapped and a crash dump is created to assist with further analysis. 
Applications receive a `FatalInternalException` for this case, with the 
`InnerException` set to the originating `AccessViolationException`.
-
-This requires the availability of `dbghelp.dll` on Windows, either in the same 
directory as `gfcppcache.dll` or in the system `PATH`. The file is installed by 
default, though for Windows 2000 a newer version may be required for minidumps. 
For Unix systems, the `gcore` command should be available (gdb &gt; 5.2 on 
Linux; available by default in Solaris).

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/updating-entries.html.md.erb
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/client-cache/updating-entries.html.md.erb 
b/geode-docs/nativeclient/client-cache/updating-entries.html.md.erb
deleted file mode 100644
index d2f15d1..0000000
--- a/geode-docs/nativeclient/client-cache/updating-entries.html.md.erb
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title:  Updating Entries
----
-
-<a id="updating-entries__section_720D480EDB8D4578BCAB5A368D6D5512"></a>
-A cached entry can be updated using these methods:
-
--   Explicitly, when a client invokes a `put` operation on an existing entry.
--   Implicitly, when a `get` is performed on an entry that has an invalid 
value in the cache. An entry can become invalid through an explicit API call, 
through an automated expiration action, or by being created with a value of 
null.
--   Automatically, when a new entry value is distributed from another cache.
-
-Similar to entry creation, all of these operations can be aborted by a cache 
writer.
-
-The `get` function returns a direct reference to the entry value object. A 
change made using that reference is called an in-place change because it 
directly modifies the contents of the value in the local cache. For details on 
safe cache access, see [Managing the Lifetime of a Cached 
Object](managing-lifetime-cached-object.html#managing-lifetime-cached-object).
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/using-serverkeys-to-retrieve.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/using-serverkeys-to-retrieve.html.md.erb 
b/geode-docs/nativeclient/client-cache/using-serverkeys-to-retrieve.html.md.erb
deleted file mode 100644
index c4c45bf..0000000
--- 
a/geode-docs/nativeclient/client-cache/using-serverkeys-to-retrieve.html.md.erb
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title:  Using serverKeys to Retrieve a Set of Region Keys
----
-
-<a 
id="using-serverkeys-to-retrieve__section_8D2276A2D70E4F80998D26BB74F9681C"></a>
-You can retrieve the set of keys defined in the cache server process that are 
associated with the client region by using the `Region::serverKeys` API 
function. If the server region is defined as a replicate, the keys returned 
consist of the entire set of keys for the region.
-
-The following example shows how the client can programmatically call 
`serverKeys`.
-
-``` pre
-VectorOfCacheableKey keysVec;
-region->serverKeys( keysVec );
-size_t vlen = keysVec.size();
-bool foundKey1 = false;
-bool foundKey2 = false;
-for( size_t i = 0; i < vlen; i++ ) {
-    CacheableStringPtr strPtr = dynCast<CacheableStringPtr> keysVec.at( i );
-    std::string veckey = strPtr->asChar();
-    if ( veckey == "skey1" ) {
-        printf( "found skey1" );
-        foundKey1 = true;
-    }
-    if ( veckey == "skey2" ) {
-        printf( "found skey2" );
-        foundKey2 = true;
-    }
-}
-```
-
-An `UnsupportedOperationException` occurs if the client region is not a native 
client region. A `MessageException` occurs if the message received from the 
server could not be handled, which can occur if an unregistered `typeId` is 
received in the reply.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/client-cache/using-thread-safety.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/client-cache/using-thread-safety.html.md.erb 
b/geode-docs/nativeclient/client-cache/using-thread-safety.html.md.erb
deleted file mode 100644
index 0b763f4..0000000
--- a/geode-docs/nativeclient/client-cache/using-thread-safety.html.md.erb
+++ /dev/null
@@ -1,13 +0,0 @@
----
-title:  Using Thread Safety in Cache Management
----
-
-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.
-
-Other non-structural operations, like region gets, puts, and queries, are 
thread safe, and you can perform them in a multithreaded way. There are caveats 
to this, for example, when two threads update the same key simultaneously, 
there is no way to determine which thread's operation will prevail.
-
-You may need to protect cached objects from concurrent usage and modification. 
The native client does not guard cached objects themselves from concurrent 
access.
-
-Always catch and handle exceptions that may be thrown, for problems like 
trying to create a `Pool` with the same name more than once.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/10-Continuous_Querying-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/10-Continuous_Querying-1.gif 
b/geode-docs/nativeclient/common/images/10-Continuous_Querying-1.gif
deleted file mode 100644
index ca78bc9..0000000
Binary files 
a/geode-docs/nativeclient/common/images/10-Continuous_Querying-1.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/10-Continuous_Querying-3.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/10-Continuous_Querying-3.gif 
b/geode-docs/nativeclient/common/images/10-Continuous_Querying-3.gif
deleted file mode 100644
index 716aabc..0000000
Binary files 
a/geode-docs/nativeclient/common/images/10-Continuous_Querying-3.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/6-DotNet_API-1.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/6-DotNet_API-1.gif 
b/geode-docs/nativeclient/common/images/6-DotNet_API-1.gif
deleted file mode 100644
index 0ac6fa0..0000000
Binary files a/geode-docs/nativeclient/common/images/6-DotNet_API-1.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/7-Preserving_Data-2.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/7-Preserving_Data-2.gif 
b/geode-docs/nativeclient/common/images/7-Preserving_Data-2.gif
deleted file mode 100644
index 9f4fde9..0000000
Binary files a/geode-docs/nativeclient/common/images/7-Preserving_Data-2.gif 
and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/client-cache-data-flow.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/client-cache-data-flow.gif 
b/geode-docs/nativeclient/common/images/client-cache-data-flow.gif
deleted file mode 100644
index b69ad60..0000000
Binary files a/geode-docs/nativeclient/common/images/client-cache-data-flow.gif 
and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/client-cache-plugins-run.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/client-cache-plugins-run.gif 
b/geode-docs/nativeclient/common/images/client-cache-plugins-run.gif
deleted file mode 100644
index f255b33..0000000
Binary files 
a/geode-docs/nativeclient/common/images/client-cache-plugins-run.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/client-server-arch.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/client-server-arch.gif 
b/geode-docs/nativeclient/common/images/client-server-arch.gif
deleted file mode 100644
index 5a1c5c6..0000000
Binary files a/geode-docs/nativeclient/common/images/client-server-arch.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/data-dep-func-from-client.gif
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/common/images/data-dep-func-from-client.gif 
b/geode-docs/nativeclient/common/images/data-dep-func-from-client.gif
deleted file mode 100644
index a0c4488..0000000
Binary files 
a/geode-docs/nativeclient/common/images/data-dep-func-from-client.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/data-dep-func-with-filter.gif
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/common/images/data-dep-func-with-filter.gif 
b/geode-docs/nativeclient/common/images/data-dep-func-with-filter.gif
deleted file mode 100644
index f5bb9d9..0000000
Binary files 
a/geode-docs/nativeclient/common/images/data-dep-func-with-filter.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/data-indep-func-from-client.gif
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/common/images/data-indep-func-from-client.gif 
b/geode-docs/nativeclient/common/images/data-indep-func-from-client.gif
deleted file mode 100644
index 1ab8a96..0000000
Binary files 
a/geode-docs/nativeclient/common/images/data-indep-func-from-client.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/delta-propagation-in-client-server.gif
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/common/images/delta-propagation-in-client-server.gif 
b/geode-docs/nativeclient/common/images/delta-propagation-in-client-server.gif
deleted file mode 100644
index e662062..0000000
Binary files 
a/geode-docs/nativeclient/common/images/delta-propagation-in-client-server.gif 
and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/delta-propagation.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/delta-propagation.gif 
b/geode-docs/nativeclient/common/images/delta-propagation.gif
deleted file mode 100644
index aa6c27e..0000000
Binary files a/geode-docs/nativeclient/common/images/delta-propagation.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/ha-data-dep-func.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/ha-data-dep-func.gif 
b/geode-docs/nativeclient/common/images/ha-data-dep-func.gif
deleted file mode 100644
index 519dd6b..0000000
Binary files a/geode-docs/nativeclient/common/images/ha-data-dep-func.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/native-client-overview.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/native-client-overview.gif 
b/geode-docs/nativeclient/common/images/native-client-overview.gif
deleted file mode 100644
index a71a23a..0000000
Binary files a/geode-docs/nativeclient/common/images/native-client-overview.gif 
and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/security-client-connections.gif
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/common/images/security-client-connections.gif 
b/geode-docs/nativeclient/common/images/security-client-connections.gif
deleted file mode 100644
index af8fd27..0000000
Binary files 
a/geode-docs/nativeclient/common/images/security-client-connections.gif and 
/dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/common/images/xact-run-from-client.gif
----------------------------------------------------------------------
diff --git a/geode-docs/nativeclient/common/images/xact-run-from-client.gif 
b/geode-docs/nativeclient/common/images/xact-run-from-client.gif
deleted file mode 100644
index 4fe2d26..0000000
Binary files a/geode-docs/nativeclient/common/images/xact-run-from-client.gif 
and /dev/null differ

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/connection-pools/about-connection-pools.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/connection-pools/about-connection-pools.html.md.erb 
b/geode-docs/nativeclient/connection-pools/about-connection-pools.html.md.erb
deleted file mode 100644
index a8e90ac..0000000
--- 
a/geode-docs/nativeclient/connection-pools/about-connection-pools.html.md.erb
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title:  Connection Pools
----
-
-Clients contain connection pools. Each region is associated with a connection 
pool using a region attribute, and operations on the region use connections 
from the respective pools.
-
-The server connectivity options are specified in the connection pool 
configuration. Each pool has a minimum and maximum number of connections.
-
-Each cache operation that requires server connectivity obtains a connection 
from the pool for the server group that the operation affects, performs the 
operation using the connection, and returns the connection to the pool. If the 
pool size is less than the maximum number of connections and all connections 
are in use, the connection pool creates a new connection and returns it. If the 
pool is at the maximum number of connections, that thread blocks until a 
connection becomes available or a `free-connection-timeout` occurs. If a 
`free-connection-timeout` occurs, an `AllConnectionsInUse` exception is thrown.
-
-The connection pool has a configurable timeout period that is used to expire 
idle connections. The idle connections are expired until the pool has the 
minimum number of connections. A monitoring thread expires idle connections, 
adds sufficient connections to bring up the count to minimum, and closes 
connections whose lifetime has been exceeded. See the 
`load-conditioning-interval` and `idle-timeout` attributes of the 
[&lt;pool&gt;](../../reference/topics/client-cache.html#cc-pool) element. A 
separate thread (ping) tests each connected endpoint for its status and if the 
endpoint is not reachable, the thread closes all connections that have been 
made to the endpoint. See the `ping-interval` attribute of the &lt;pool&gt; 
element&gt;.
-
-<a id="client-load-balancing__fig_226964BAA1464DBA9F5CEDC2CB7B3585"></a>
-<span class="figtitleprefix">Figure: </span>Logical Architecture of 
Client/Server Connections
-
-<img src="../common/images/client-server-arch.gif" 
id="client-load-balancing__image_1E8316666E1B4CC2ADE4D927B629E49F" 
class="image" />
-
-When a connection receives an exception, the operation is failed over to 
another connection from the pool. The failover mechanism obtains the endpoint 
to failover to from the locator or from the specified endpoint list in the pool.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/connection-pools/about-server-locators.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/connection-pools/about-server-locators.html.md.erb 
b/geode-docs/nativeclient/connection-pools/about-server-locators.html.md.erb
deleted file mode 100644
index 69bc6c5..0000000
--- a/geode-docs/nativeclient/connection-pools/about-server-locators.html.md.erb
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title:  Server Locators
----
-
-Server locators continuously monitor server availability and server load 
information. The client is configured with a list of server locators and 
consults a server locator to request a connection to a server in the 
distributed system.
-
-Locators provide clients with dynamic server discovery and server load 
balancing. They give clients connection information for the server with the 
least load at any given time.
-
-Server locators provide these main features:
-
--   **Automated discovery of servers and locators**. Adding and removing 
servers or locators is made easy as each client does not require a list of 
servers to be configured at the time of pool creation.
--   **Client load rebalancing**. Server locators give clients dynamic server 
information and provide server load rebalancing after servers depart or join 
the system.
--   **High availability**. When a client/server connection receives an 
exception, the connection is automatically failed over to another available 
connection in the pool. Redundancy is also provided for client subscriptions.
-
-Alternatively, you can configure a pool statically with a list of endpoints. 
When the pools are statically configured, a round-robin load balancing policy 
is used to distribute connections across the servers.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/connection-pools/client-load-balancing.html.md.erb
----------------------------------------------------------------------
diff --git 
a/geode-docs/nativeclient/connection-pools/client-load-balancing.html.md.erb 
b/geode-docs/nativeclient/connection-pools/client-load-balancing.html.md.erb
deleted file mode 100644
index 98d56ab..0000000
--- a/geode-docs/nativeclient/connection-pools/client-load-balancing.html.md.erb
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title:  How Client Load Balancing Works
----
-
-In a distributed system, servers can be added or removed and their capacity to 
service new client connections may vary. The server connectivity options are 
specified in the connection pool configuration.
-
-The Geode connection pool API supports connecting to servers through server 
locators or directly connecting to servers.
-
--   **[Server 
Locators](../../nativeclient/connection-pools/about-server-locators.html)**
-
-    Server locators continuously monitor server availability and server load 
information. The client is configured with a list of server locators and 
consults a server locator to request a connection to a server in the 
distributed system.
-
--   **[Connection 
Pools](../../nativeclient/connection-pools/about-connection-pools.html)**
-
-    Clients contain connection pools. Each region is associated with a 
connection pool using a region attribute, and operations on the region use 
connections from the respective pools.
-
--   **[Discovering Locators 
Dynamically](../../nativeclient/connection-pools/discovering-locators-dynamically.html)**
-
-    A background thread periodically queries the locator for any other 
locators joining the distributed system.
-
-

Reply via email to