[10/50] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[sbawaskar]

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..000
--- a/geode-docs/nativeclient/client-cache/disk-policy.html.md.erb
+++ /dev/null
@@ -1,34 +0,0 @@

-title:  DiskPolicy

-
-
-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
-
-  
-
-```
-
-Overflow requires a persistence manager for cache-to-disk and disk-to-cache 
operations. See 
[PersistenceManager](persistence-manager.html#persistence-manager).
-
-## 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.
-
-
-
-Figure: Data Flow Between Overflow Region 
and Disk Files
-
-
-
-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..000
--- 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..000
--- a/geode-docs/nativeclient/client-cache/expiration-attributes.html.md.erb
+++ /dev/null
@@ -1,65 +0,0 @@

-title:  Specifying Expiration Attributes

-
-
-Expiration 

[10/50] [abbrv] incubator-geode git commit: GEODE-1952: removed native client docs, set aside until native client code is merged in (see GEODE-1964)

[upthewaterspout]

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 
Authored: Tue Oct 4 17:15:37 2016 -0700
Committer: Dave Barnes 
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 --