incubator-geode git commit: GEODE-420: Adding test to SSLConfigurationFactoryJUnitTest.java to test for non-ssl configurations

[udo]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop 18c2dc3fb -> f3b0d0e15


GEODE-420: Adding test to SSLConfigurationFactoryJUnitTest.java to test for 
non-ssl configurations


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

Branch: refs/heads/develop
Commit: f3b0d0e15df54b4014dbec976c62cfbdde6f34db
Parents: 18c2dc3
Author: Udo Kohlmeyer 
Authored: Wed Oct 5 11:31:30 2016 +1100
Committer: Udo Kohlmeyer 
Committed: Wed Oct 5 11:31:30 2016 +1100

--
 .../net/SSLConfigurationFactoryJUnitTest.java   | 37 
 1 file changed, 23 insertions(+), 14 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/f3b0d0e1/geode-core/src/test/java/org/apache/geode/internal/net/SSLConfigurationFactoryJUnitTest.java
--
diff --git 
a/geode-core/src/test/java/org/apache/geode/internal/net/SSLConfigurationFactoryJUnitTest.java
 
b/geode-core/src/test/java/org/apache/geode/internal/net/SSLConfigurationFactoryJUnitTest.java
index 29ef943..80d195d 100644
--- 
a/geode-core/src/test/java/org/apache/geode/internal/net/SSLConfigurationFactoryJUnitTest.java
+++ 
b/geode-core/src/test/java/org/apache/geode/internal/net/SSLConfigurationFactoryJUnitTest.java
@@ -41,6 +41,16 @@ public class SSLConfigurationFactoryJUnitTest {
   }
 
   @Test
+  public void getNonSSLConfiguration() throws Exception {
+Properties properties = new Properties();
+DistributionConfigImpl distributionConfig = new 
DistributionConfigImpl(properties);
+SSLConfigurationFactory.setDistributionConfig(distributionConfig);
+for (SecurableCommunicationChannel securableComponent : 
SecurableCommunicationChannel.values()) {
+  assertSSLConfig(properties, 
SSLConfigurationFactory.getSSLConfigForComponent(securableComponent), 
securableComponent, distributionConfig);
+}
+  }
+
+  @Test
   public void getSSLConfigWithCommaDelimitedProtocols() throws Exception {
 Properties properties = new Properties();
 properties.setProperty(SSL_ENABLED_COMPONENTS, "all");
@@ -157,21 +167,20 @@ public class SSLConfigurationFactoryJUnitTest {
 }
   }
 
-  private void assertSSLConfig(final Properties properties,
-   final SSLConfig sslConfig,
-   final SecurableCommunicationChannel 
expectedSecurableComponent,
-   final DistributionConfigImpl 
distributionConfig) {
+  private void assertSSLConfig(final Properties properties, final SSLConfig 
sslConfig, final SecurableCommunicationChannel expectedSecurableComponent, 
final DistributionConfigImpl distributionConfig) {
 assertEquals(isSSLComponentEnabled(expectedSecurableComponent, 
distributionConfig.getSecurableCommunicationChannels()), sslConfig.isEnabled());
-assertEquals(properties.getProperty(SSL_KEYSTORE), 
sslConfig.getKeystore());
-assertEquals(properties.getProperty(SSL_KEYSTORE_PASSWORD), 
sslConfig.getKeystorePassword());
-assertEquals(properties.getProperty(SSL_KEYSTORE_TYPE), 
sslConfig.getKeystoreType());
-assertEquals(properties.getProperty(SSL_TRUSTSTORE), 
sslConfig.getTruststore());
-assertEquals(properties.getProperty(SSL_TRUSTSTORE_PASSWORD), 
sslConfig.getTruststorePassword());
-assertEquals(properties.getProperty(SSL_CIPHERS).replace(","," "), 
sslConfig.getCiphers());
-assertEquals(properties.getProperty(SSL_PROTOCOLS).replace(","," "), 
sslConfig.getProtocols());
-assertEquals(getCorrectAlias(expectedSecurableComponent, properties), 
sslConfig.getAlias());
-assertEquals(requiresAuthentication(properties, 
expectedSecurableComponent), sslConfig.isRequireAuth());
-assertEquals(expectedSecurableComponent, 
sslConfig.getSecuredCommunicationChannel());
+if (sslConfig.isEnabled()) {
+  assertEquals(properties.getProperty(SSL_KEYSTORE), 
sslConfig.getKeystore());
+  assertEquals(properties.getProperty(SSL_KEYSTORE_PASSWORD), 
sslConfig.getKeystorePassword());
+  assertEquals(properties.getProperty(SSL_KEYSTORE_TYPE), 
sslConfig.getKeystoreType());
+  assertEquals(properties.getProperty(SSL_TRUSTSTORE), 
sslConfig.getTruststore());
+  assertEquals(properties.getProperty(SSL_TRUSTSTORE_PASSWORD), 
sslConfig.getTruststorePassword());
+  assertEquals(properties.getProperty(SSL_CIPHERS).replace(",", " "), 
sslConfig.getCiphers());
+  assertEquals(properties.getProperty(SSL_PROTOCOLS).replace(",", " "), 
sslConfig.getProtocols());
+  assertEquals(getCorrectAlias(expectedSecurableComponent, 

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

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb 
b/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb
deleted file mode 100644
index 0bdda28..000
--- a/geode-docs/nativeclient/cpp-caching-api/pdx_auto_serialization.html.md.erb
+++ /dev/null
@@ -1,355 +0,0 @@

-title: Using Automatic PDX Serialization

-
-You can allow your native client C++ applications to automatically PDX 
serialize and deserialize domain objects without having to add any extra code 
by using the `pdxautoserializer` command line tool provided with the native 
client.
-
-When using the native client C++ API, you can automatically serialize and 
deserialize domain objects without making any code changes to those objects or 
having to implement a `PdxSerializer` or `PdxSerializable` interface and their 
related `fromData` and `toData` methods. The Geode native client includes a 
command-line utility, `pdxautoserializer`, that allows you to generate C++ code 
that will serialize your domain objects in the PDX format for you.
-
-## How to Use Automatic PDX 
Serialization
-
-**Prerequisites:**
-
--   Understand generally how to configure the Geode cache.
-
--   Understand how PDX serialization works and how to configure your 
application to use PdxSerializer.
-
-The procedure below uses the following sample class:
-
-``` pre
-class PortfolioPdx 
-{
-  private:
-int32_t id;
-char* pkid;
-PositionPdxPtr position1;
-PositionPdxPtr position2;
-CacheableHashMapPtr positions;
-char** names;
-int8_t* newVal;
-CacheableDatePtr creationDate;
-int8_t* arrayNull;
-int8_t* arrayZeroSize;
-  public:
-// CTOR
-// DTORS
-// Other Methods declarations
-```
-
-For each domain class you provide, all fields are considered for serialization 
except those defined as static or transient and those you explicitly exclude 
using macros.
-
-1.  Inherit your class from `gemfire::PdxSerializable`.
-
-``` pre
-class PortfolioPdx : public PdxSerializable
-```
-
-2.  Add the following method declarations in the public part of the class.
-
-``` pre
-const char* getClassName() const;
-virtual void toData(gemfire::PdxWriterPtr pw);
-virtual void fromData(gemfire::PdxReaderPtr pr);
-static PdxSerializable* createDeserializable();
-```
-
-3.  In your pre-build environment (for example in your **makefiles**), call 
`pdxautoserializer` as follows:
-
-``` pre
-/bin/pdxautoserializer.exe --outDir= 
/PortfolioPdx.hpp
-```
-
-4.  Include the generated file in your project and compile.
-
-The following is an example of a generated file:
-
-``` pre
-#include "PortfolioPdx.hpp"
-#include 
-#include 
-#include 
-namespace testobject
-{
-  void PortfolioPdx::toData(gemfire::PdxWriterPtr var)
-  {
-gemfire::PdxAutoSerializable::writePdxObject(var, "id", id);
-gemfire::PdxAutoSerializable::writePdxObject(var, "pkid", pkid);
-gemfire::PdxAutoSerializable::writePdxObject(var, "position1", position1);
-gemfire::PdxAutoSerializable::writePdxObject(var, "position2", position2);
-gemfire::PdxAutoSerializable::writePdxObject(var, "positions", positions);
-gemfire::PdxAutoSerializable::writePdxObject(var, "status", status);
-gemfire::PdxAutoSerializable::writePdxObject(var, "creationDate", 
creationDate);
-  }
-
-  void PortfolioPdx::fromData(PdxReaderPtr var)
-  {
-gemfire::PdxAutoSerializable::readPdxObject(var, "id", id);
-gemfire::PdxAutoSerializable::readPdxObject(var, "pkid", pkid);
-gemfire::PdxAutoSerializable::readPdxObject(var, "position1", position1);
-gemfire::PdxAutoSerializable::readPdxObject(var, "position2", position2);
-gemfire::PdxAutoSerializable::readPdxObject(var, "positions", positions);
-gemfire::PdxAutoSerializable::readPdxObject(var, "status", status);
-gemfire::PdxAutoSerializable::readPdxObject(var, "creationDate", 
creationDate);
-  }
-  
-  const char* PortfolioPdx::getClassName()  const
-  {
- return "PortfolioPdx";
-  }
-}
-```
-
-## Handling Arrays
-
-1.  Define the following macro in your header file:
-
-``` pre
-#define GFARRAYSIZE(x)
-```
-
-2.  Assuming that the following is the class member of type array:
-
-``` pre
-int8_t* newVal;
-```
-
-Then define a new variable which sets the length of the array:
-
-``` pre
-int32_t newValSize;
-```
-
-3.  Tag the new variable with the `GFARRAYSIZE` macro as follows:
-
-``` pre
-GFARRAYSIZE(newVal) int32_t newValSize;
-```
-
-## Using a Single Variable as Length for Multiple Arrays
-
-You can use the GFARRAYSIZES to have single length for multiple arrays.
-
-Define the GFARRAYSIZES macro as follows:
-
-``` pre
-#define 

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

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb 
b/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb
deleted file mode 100644
index da707bc..000
--- a/geode-docs/nativeclient/introduction/developing-solaris.html.md.erb
+++ /dev/null
@@ -1,44 +0,0 @@

-title:  Developing C++ Programs on Solaris

-
-This section describes how to build and run a native client application on 
Solaris.
-
-## Step 1. Set Environment Variables
-
-**Note:** When compiling external projects or applications that are used or 
referenced by the native client, make sure that you compile them for the same 
target architecture as your native client installation. For example, if you 
installed the 32-bit (x86) version of the native client, compile your external 
projects for 32-bit (x86) architecture.
-
-Set the native client environment variables on each Solaris host. For each 
case, *productDir* is the path to the native client product directory.
-
-**For Bourne and Korn shells (sh, ksh, bash)**
-
-``` pre
-GFCPP=; export GFCPP
-PATH=$GFCPP/bin:$PATH;export PATH
-LD_LIBRARY_PATH=$GFCPP/lib:$LD_LIBRARY_PATH;export LD_LIBRARY_PATH
-```
-
-## Step 2. Compile C++ Clients and Dynamically Link to 
Them to Native Client Library
-
-Version 5.9 of the *SUNpro* compiler is supported on Solaris. The linker 
switches vary according to whether you are statically linking to the native 
client library.
-
-To build and link a C++ client on Solaris, the compilation command line must 
include the appropriate arguments from this table.
-
-
-
-| Argument 
  | Explanation|
-|||
-| `-D_REENTRANT`   
  | Required to compile Solaris programs in a thread-safe way. |
-| `-xarch=v8plus`  
  | Enables 32-bit compilation.|
-| `-xarch=v9`  
  | Enables 64-bit compilation.|
-| `-ldl`; `-lpthread`; `-lc`; `-lm`; `-lsocket`; `-lrt`; `-lnsl`; 
`-ldemangle`; `-lkstat`; `-lz` | Additional libraries.  
|
-| `-library=stlport4`  
  | Solaris library compilation.   |
-| `-I$ GFCPP /include` 
  | Specifies the GemFire include directory.   |
-
-
-
-## Step 3. Make Sure the Native Client Library Can Be 
Loaded
-
-When a C++ application is not statically linked to the native client library, 
the library must be dynamically loadable.
-
-To verify that the native client library is available for loading, make sure 
you have added the path *productDir*`/lib` to the *LD\_LIBRARY\_PATH* 
environment variable, where *productDir* is the path to the Geode product 
directory.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/introduction/developing-windows.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/introduction/developing-windows.html.md.erb 
b/geode-docs/nativeclient/introduction/developing-windows.html.md.erb
deleted file mode 100644
index 7ed37c0..000
--- a/geode-docs/nativeclient/introduction/developing-windows.html.md.erb
+++ /dev/null
@@ -1,56 +0,0 @@

-title:  Developing C++ Programs on Windows

-
-Geode uses the Visual Studio 2010 Service Pack 1 compiler for C++ programs on 
Windows, which invokes Microsoft® `cl.exe` from the command line at 
compile time.
-
-The Geode native client supports .NET 4.0 and Visual Studio 2010. For 
advantages and more information on the features of .NET 4.0 and Visual Studio 
2010 SP1, see 
[http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/dd831853(v=vs.100).aspx)
 and 
[http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx](http://msdn.microsoft.com/en-us/library/vstudio/w0x726c2(v=vs.100).aspx).
-
-Visual Studio 2010 SP1 is the recommended compiler. If you are using any other 
compiler, contact technical support for assistance.
-
-**Note:** When compiling external projects or applications that are used or 
referenced by the native client, make sure that you compile them for the same 

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

[dbarnes]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEODE-1952 ccc2fbda4 -> 381d0faae


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb 
b/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb
deleted file mode 100644
index d753366..000
--- a/geode-docs/nativeclient/sqlite-persistence/windows_install.html.md.erb
+++ /dev/null
@@ -1,37 +0,0 @@

-title:  Windows Installation

-
-This topic describes how to install the SQLite Persistence Manager on Windows 
for use with the Geode native client.
-
-The Geode Native Client has been tested with SQLite v3.7.14.1.
-
-The productDir directory refers to the native client 
product directory path.
-
-The following libraries are required. The productDir/bin 
directory containing these libraries must be present in the Windows `PATH` 
environment variable, and that directory is added to `PATH` during the Geode 
product installation.
-
--   The `sqliteimpl.dll` and `GemStone.GemFire.Plugins.SQLite.dll` files are 
provided in productDir/bin.
--   For .NET C\# native client application development, you need to obtain the 
`System.Data.SQLite.dll` SQLite library, as described below. The library can be 
copied to productDir/bin.
--   For C++ native client application development, you need the `SqLite3.dll` 
SQLite Library. You create this library and make it available in the runtime 
linking path, or copied to productDir/bin, as described 
below.
-
-## Downloading Pre-built System.Data.SQLite.dll Binaries
-
-If you are writing native client applications using the .NET caching API, 
obtain the SQLite library (version 3.12.2 or later) for Windows as follows:
-
-1.  Access the System.Data.SQLite Download Page at the following URL: 
[http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki](http://system.data.sqlite.org/index.html/doc/trunk/www/downloads.wiki).
-2.  Download the appropriate setup file for your .NET Framework installation 
and hardware architecture.
--   For 64-bit Windows, under **Precompiled Binaries for 64-bit Windows 
(.NET Framework 4.5.1)** download 
`sqlite-netFx451-binary-bundle-x64-2013-1.0.101.0.zip`.
-
-3.  Execute the setup .exe file, and follow the prompts in the installation 
wizard. Accept all default installation options.
-4.  Copy the `C:\Program 
Files\System.Data.SQLite\2010\bin\System.Data.SQLite.dll` file to your Geode 
Native Client distribution at `productDir\bin`.
-
-## Downloading, Building, and Installing the Library
-
-If you are writing native client applications using the C++ caching API, you 
need to build the SQLite solution for your Windows platform architecture.
-
-1.  Download the source code `sqlite-autoconf-NNN.tar.gz` file (where 
*NNN* corresponds to the version) for SQLite version 3.12.2 or later from 
[http://www.sqlite.org/download.html](http://www.sqlite.org/download.html).
-2.  Extract the source code from the .tar.gz file. You may need to use CygWin 
or a Windows-compatible tar extraction tool.
-3.  Using Visual Studio, build the version-specific SqLite solution either as 
a release or debug build:
--   If you are using 64-bit Windows, use the x64 configuration.
-
-4.  From the built files, copy the `SqLite3.dll` file to your Geode Native 
Client distribution at productDir/bin.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
 
b/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
deleted file mode 100644
index 0edcb18..000
--- 
a/geode-docs/nativeclient/system-statistics/cache_performance_statistics.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@

-title:  Cache Performance Statistics

-
-Use cache performance statistics to determine the type and number of cache 
operations being performed and how much time they consume.
-
-These statistics are available if the member creates a cache.
-
-|  |   
   |
-|--|--|
-| `creates`| Total number of cache creates.
   |
-| `puts`   | Total number of cache puts.   
   |
-| `gets`   | Total number of cache gets.  

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

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
 
b/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
deleted file mode 100644
index eac1907..000
--- 
a/geode-docs/nativeclient/delta-propagation/how-delta-propagation-works.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@

-title:  How Delta Propagation Works

-
-Geode propagates object deltas using methods that you program on the client 
side. The methods are in the delta interface, which you implement in your 
cached objects’ classes.
-
-This figure shows delta propagation for a change to an entry with key, `k`, 
and value object, `v`.
-
-
-Figure: Delta Propagation
-
-
-
-1.  **get operation**. The `get` works as usual; the cache returns the full 
entry object from the local cache or, if it is unavailable there, from a server 
cache or from a loader.
-2.  **update methods**. You need to add code to the object’s update methods 
so that they save delta information for object updates, in addition to the work 
they were already doing.
-3.  **put operation**. The `put` works as usual in the local cache, using the 
full value, then calls `hasDelta` to check for deltas and `toDelta` to 
serialize the information.
-4.  **receipt of delta**. `fromDelta` extracts the delta information that was 
serialized by `toDelta` and applies it to the object in the local cache. The 
delta is applied directly to the existing value or to a clone, depending on how 
you configure it for the region.
-5.  **additional distributions**. As with full distributions, receiving 
members forward the delta according to their configurations and connections to 
other members. In the example, the server would forward the delta to its peers 
and its other clients as needed. Receiving members do not recreate the delta; 
`toDelta` is only called in the originating member.
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
 
b/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
deleted file mode 100644
index 6d1c3ee..000
--- 
a/geode-docs/nativeclient/delta-propagation/implementing-delta-propagation.html.md.erb
+++ /dev/null
@@ -1,41 +0,0 @@

-title:  Implementing Delta Propagation

-
-By default, delta propagation is enabled in your distributed system and is 
used for objects that implement the delta interface. You program the 
client-side methods to extract delta information for your entries and to apply 
received delta information.
-
-For more information, see [Delta Propagation 
API](delta-propagation-api.html#delta-propagation-api).
-
-**Prerequisites**
-
--   Study your object types and expected application behavior to determine 
which objects should use delta propagation. Delta propagation is not beneficial 
for all data and data modification scenarios. See [Exceptions and 
Limitations](performance.html#performance).
--   Decide whether to enable cloning. Cloning is disabled by default. See 
[cloning-enabled](delta-propagation-properties.html#delta-propagation-properties).
--   If you enable cloning, consider providing your own implementation, to 
optimize performance.
--   If you do not enable cloning, be sure to synchronize your delta code.
--   If you do not enable cloning, review all associated listener code for 
dependencies on the entry event old value. Without cloning, Geode modifies the 
entry in place and so loses its reference to the old value. For delta events, 
the `EntryEvent` methods to retrieve the old and new values both return the new 
value.
-
-**Procedure**
-
-For every class in which you want delta propagation, implement the delta 
interface and update your methods to support delta propagation. Exactly how you 
do this depends on your application and object needs, but these steps describe 
the basic approach.
-
-1.  Study the object contents to decide how to handle delta changes.
-
-Delta propagation has the same issues of distributed concurrency control 
as the distribution of full objects, but on a more detailed level. Some parts 
of your objects may be able to change independent of one another while others 
may always need to change together. Send deltas large enough to keep your data 
logically consistent. If, for example, field A and field B depend on each 
other, then your delta distributions should either update both fields or 
neither. As with regular updates, the fewer producers you have on a data 
region, the lower your likelihood of 

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

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb 
b/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb
deleted file mode 100644
index ac11128..000
--- 
a/geode-docs/nativeclient/programming-examples/serialization-java.html.md.erb
+++ /dev/null
@@ -1,210 +0,0 @@

-title:  Java Serialization Example

-
-## Implementing an Embedded Object (Java)
-
-``` pre
-public class User implements DataSerializable
-{
-private String name;
-private int userId;
-private ExampleObject eo;
-static {
-Instantiator.register(
-   new Instantiator(User.class, (byte)45)
-   {
-public DataSerializable newInstance() {
-return new User();
-}
-} );
-}
-/**
- * Creates an "empty" User whose contents are filled in by
- * invoking its toData() method
- */
-
-private User() {
-this.name = "";
-this.userId = 0;
-this.eo = new ExampleObject(0);
-}
-
-public User(String name, int userId) {
-this.name = name;
-this.userId = userId;
-this.eo = new ExampleObject(userId);
-}
-
-public void setEO(ExampleObject eo) {
-this.eo = eo;
-}
-
-public ExampleObject getEO() {
-return eo;
-}
-
-public void toData(DataOutput out) throws IOException {
-out.writeUTF(this.name);
-out.writeInt(this.userId);
-eo.toData(out);
-}
-
-public void fromData(DataInput in) throws IOException,
- ClassNotFoundException {
-this.name = in.readUTF();
-this.userId = in.readInt();
-this.eo.fromData(in);
-}
-
-public int getUserId() {
-return userId;
-}
-
-public String getName() {
-return name;
-}
-
-public boolean equals(User o) {
-if (!this.name.equals(o.name)) return false;
-if (this.userId != o.userId) return false;
-if (!this.eo.equals(o.eo)) return false;
-return true;
-}
-}
-```
-
-## Implementing Complex Data Types (Java)
-
-``` pre
-public class ExampleObject implements DataSerializable {
-private double double_field;
-private long long_field;
-private float float_field;
-private int int_field;
-private short short_field;
-private java.lang.String string_field;
-private Vector string_vector;
-static {
-Instantiator.register(new Instantiator(ExampleObject.class, (byte) 46) 
{
-public DataSerializable newInstance() {
-return new ExampleObject();
-}
-});
-}
-public ExampleObject( ) {
-this.double_field = 0.0D;
-this.long_field = 0L;
-this.float_field = 0.0F;
-this.int_field = 0;
-this.short_field = 0;
-this.string_field = null;
-this.string_vector = null;
-}
-public ExampleObject(int id) {
-this.int_field = id;
-this.string_field = String.valueOf(id);
-this.short_field = Short.parseShort(string_field);
-this.double_field = Double.parseDouble(string_field);
-this.float_field = Float.parseFloat(string_field);
-this.long_field = Long.parseLong(string_field);
-this.string_vector = new Vector();
-for (int i=0; i<3; i++) {
-this.string_vector.addElement(string_field);
-}
-}
-public ExampleObject(String id_str) {
-this.int_field = Integer.parseInt(id_str);
-this.string_field = id_str;
-this.short_field = Short.parseShort(string_field);
-this.double_field = Double.parseDouble(string_field);
-this.float_field = Float.parseFloat(string_field);
-this.long_field = Long.parseLong(string_field);
-this.string_vector = new Vector();
-for (int i=0; i<3; i++) {
-this.string_vector.addElement(string_field);
-}
-}
-public double getDouble_field( ) {
-return this.double_field;
-}
-public void setDouble_field( double double_field ) {
-this.double_field = double_field;
-}
-public long getLong_field( ) {
-return this.long_field;
-}
-public void setLong_field( long long_field ) {
-this.long_field = long_field;
-}
-public float getFloat_field( ) {
-return this.float_field;
-}
-public void setFloat_field( float float_field ) {
-this.float_field = float_field;
-}
-public int getInt_field( ) {
-return this.int_field;
-}
-public void setInt_field( int int_field ) {
-   

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

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
 
b/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
deleted file mode 100644
index d4c2ba3..000
--- 
a/geode-docs/nativeclient/remote-querying/96-progexamples/3-query-code-examples-structset.html.md.erb
+++ /dev/null
@@ -1,192 +0,0 @@

-title:  Query Code Samples Returning StructSet

-
-These examples return a `StructSet` for built-in and user-defined data types, 
`Struct` objects, and collections.
-
-## Query Returning a StructSet for a Built-In Data Type
-
-``` pre
-QueryServicePtr qrySvcPtr = cachePtr->getQueryService("examplePool");
-const char * querystring =
-   "SELECT DISTINCT ID, pkid, status, getType FROM /portfolios";
-QueryPtr query = qrySvcPtr->newQuery(querystring);
-//specify 10 seconds for the query timeout period
-SelectResultsPtr results = query->execute(10);
-if (results == NULLPTR)
-{
-   printf( "\nNo results returned from the server");
-}
-//obtaining a handle to resultset
-StructSetPtr ss(dynamic_cast (results.ptr()));
-if (ss == NULLPTR)
-{
-   printf ("\nStructSet is not obtained \n");
-   return;
-}
-//iterating through the resultset using indexes.
-for ( int32_t row=0; row < ss->size(); row++)
-{
-   Struct * siptr = (Struct*) dynamic_cast ( ((*ss)[row]).ptr() );
-   if (siptr == NULL)
-   {
-  printf("\nstruct is empty \n");
-  continue;
- 
-}
-//iterate through fields now
-for( int32_t field=0; field < siptr->length(); field++)
-{
-   SerializablePtr fieldptr((*siptr)[field]);
-   if(fieldptr == NULLPTR )
-   {
-  printf("\nnull data received\n");
-   }
-   CacheableStringPtr
-  str(dynamic_cast(fieldptr.ptr()));
-   if (str == NULLPTR)
-   {
-  printf("\n field is of some other type \n");
-   }
-   else
-   {
-  printf("\n Data for %s is %s ", siptr->getFieldName(field), 
str->asChar() );
-   }
-} //end of columns
- } // end of rows
-```
-
-## Returning Struct Objects
-
-``` pre
-QueryServicePtr qrySvcPtr = cachePtr->getQueryService("examplePool");
-const char * querystring =
-   "SELECT DISTINCT derivedProjAttrbts, key: p.key FROM "
-   "/Portfolios.entries p, (SELECT DISTINCT x.ID, myPos.secId FROM "
-   "/Portfolios x, x.positions.values AS myPos) derivedProjAttrbts WHERE "
-   "p.value.ID = derivedProjAttrbts.ID AND derivedProjAttrbts.secId = 'IBM'";
-QueryPtr query = qrySvcPtr->newQuery(querystring);
-//specify 10 seconds for the query timeout period
-SelectResultsPtr results = query->execute(10);
-if (results == NULLPTR)
-{
-   printf( "\nNo results returned from the server");
-}
-//obtaining a handle to resultset
-StructSetPtr ss(dynamic_cast (results.ptr()));
-if (ss == NULLPTR)
-{
-   printf ("\nStructSet is not obtained \n");
-   return;
-}
-//iterating through the resultset using indexes.
-for (int32_t row=0; row < ss->size(); row++)
-{
-   Struct * siptr = (Struct*) dynamic_cast ( ((*ss)[row]).ptr() );
-   if (siptr == NULL) { printf("\nstruct is empty \n"); }
-   //iterate through fields now
-   for (int32_t field=0; field < siptr->length(); field++) {
-   SerializablePtr fieldptr((*siptr)[field]);
-   if (fieldptr == NULLPTR )
-   {
-  printf("\nnull data received\n");
-   }
-   CacheableStringPtr
-  str(dynamic_cast(fieldptr.ptr()));
-   if (str != NULLPTR) {
-  printf("\n Data for %s is %s ", siptr->getFieldName(field),
-  str->asChar() );
-   }
-   else
-   {
-  StructPtr simpl(dynamic_cast (fieldptr.ptr()));
-  if (simpl == NULLPTR)
-  {
-  printf("\n field is of some other type \n"); continue;
-  }
-  printf( "\n struct received %s \n", siptr->getFieldName(field) );
-  for (int32_t inner_field=0; inner_field < simpl->length(); 
inner_field++)
-  {
-  SerializablePtr innerfieldptr((*simpl)[inner_field]);
-  if (innerfieldptr == NULLPTR)
-  {
-  printf("\nfield of struct is NULL\n");
-  }
-  CacheableStringPtr str(dynamic_cast
- (innerfieldptr.ptr()));
-  if (str != NULLPTR)
-  {
-  printf("\n Data for %s is %s ",
-  simpl->getFieldName(inner_field),str->asChar() );
-  }
-  else
-  {
-  printf("\n some other object type inside struct\n");
-  }
-   }
-}
-} //end of columns
- 

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

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb 
b/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb
deleted file mode 100644
index b3acf2d..000
--- a/geode-docs/nativeclient/dotnet-caching-api/object-lifetimes.html.md.erb
+++ /dev/null
@@ -1,37 +0,0 @@

-title:  Object Lifetimes

-
-The .NET API provides a managed set of assemblies for the C++ API. The 
underlying C++ object will stay in memory until the .NET object is 
garbage-collected.
-
-The underlying C++ API employs reference counting using smart pointers for 
most classes. This means that all API operations with those objects return a 
reference to the underlying object and not a copy. Consequently, the underlying 
object will not be freed as long as the .NET application holds a reference to 
an object. In other words, the underlying object will stay in memory until the 
.NET object is garbage-collected. As long as a reference to an object is alive, 
the artifacts it maintains will also be alive.
-
-For example, as long as a `Region` object is not garbage-collected, then the 
destructor of the C++ native persistence manager (if any) for the region is not 
invoked.
-
-In the C++ API, the references to an object are reduced when the object goes 
out of scope for stack allocation, or is deleted explicitly for heap 
allocation. The object is destroyed when its reference count reaches zero. In 
the .NET API, the references are reduced when the object is garbage-collected 
or is explicitly disposed with the .NET `using` statement.
-
-Because a reference to the object is returned, any change to the object also 
immediately changes the object as stored internally. For example, if an object 
is put into the cache using `Region.Put`, a reference of the object is stored 
in the internal structures. If you modify the object, the internal object also 
changes. However, it is not distributed to other members of the distributed 
system until another `Region.Put` is done.
-
-To find out if a class is reference counted, look at the online API 
documentation for the class. If the class is wrapped by `UMWrap` or `SBWrap`, 
the class is reference counted.
-
-These are examples of classes that are reference counted:
-
--   `Cache`
--   `CacheStatistics`
--   `DistributedSystem`
--   `Properties`
--   `RegionAttributes`
--   `AttributesMutator`
--   `RegionEntry`
--   `Region`
--   `EntryEvent`
--   `RegionEvent`
-
-These are examples of classes that are not reference counted:
-
--   `AttributesFactory`
--   `DataInput`
--   `DataOutput`
--   `SystemProperties`
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb
--
diff --git a/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb 
b/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb
deleted file mode 100644
index 89c34e4..000
--- a/geode-docs/nativeclient/dotnet-caching-api/other-apis.html.md.erb
+++ /dev/null
@@ -1,14 +0,0 @@

-title:  Property Collections and Logging APIs

-
-This section describes classes for property collections and logging.
-
--   **Properties** **class**. Provides a collection of properties, each of 
which is a key/value pair. Each key is a string, and the value can be a string 
or an integer.
--   **Log class**. Defines methods available to clients that need to write a 
log message to their Geode system shared log file. Any attempt to use an 
instance after its connection is disconnected throws a 
**NotConnectedException**. For any logged message the log file contains:
--   The log level of the message.
--   The time the message was logged.
--   The ID of the connection and thread that logged the message.
--   The message itself, possibly with an exception including its stack 
trace.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
 
b/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
deleted file mode 100644
index fa3bbf6..000
--- 
a/geode-docs/nativeclient/dotnet-caching-api/primary-apis-cache-generic.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@

-title:  Primary APIs

-
-These are the main APIs within `GemStone::GemFire::Cache::Generic` used for 
cache, region, and data entry management in Geode .NET. For detailed 
information about the APIs, see the .NET API documentation included in the 

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

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/381d0faa/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
--
diff --git 
a/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
 
b/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
deleted file mode 100644
index 62e033b..000
--- 
a/geode-docs/nativeclient/connection-pools/configuring-pools-attributes-example.html.md.erb
+++ /dev/null
@@ -1,156 +0,0 @@

-title:  Pool Configuration Example and Settings

-
-Connection pools require standard client/server distributed system and cache 
configuration settings. You must also configure settings for the locator, 
server, and pool elements.
-
--   Locator. Host and port where a server locator is listening.
--   Server. Host and port where a server is listening.
--   Pool. Client/server connection pool.
-
-The example shows a declarative pool configuration. Following the example is a 
table that describes the attributes that can be configured.
-
-## Example—Declarative Pool Configuration
-
-This example shows a declarative pool configuration.
-
-**Note:**
-You create an instance of `PoolFactory` through `PoolManager`.
-
-``` pre
-
-   
-
-```
-
-## Pool Attributes
-
-
-
-
-
-
-
-
-
-Attribute Name
-Description
-Default
-
-
-
-
-free-connection-timeout
-Number of milliseconds (ms) that the client waits for a free connection 
if  max-connections limit is configured and all 
connections are in use.
-1 ms
-
-
-idle-timeout
-Number of milliseconds to wait for a connection to become idle for load 
balancing
-5000 ms
-
-
-load-conditioning-interval
-Interval in which the pool checks to see if a connection to a specific 
server should be moved to a different server to improve the load 
balance.
-30 ms (5 minutes)
-
-
-max-connections
-Maximum number of connections that the pool can create. If all 
connections are in use, an operation requiring a client-to server-connection is 
blocked until a connection is available or the  
free-connection-timeout is reached. If set to -1, there is no maximum. 
The setting must indicate a cap greater than  
min-connections.
-
-**Note:**
-If you use this setting to cap your pool connections, disable the pool 
attribute  pr-single-hop-enabled. Leaving single 
hop enabled can increase thrashing and lower performance.
-
--1
-
-
-min-connections
-Number of connections that must be created initially.
-5
-
-
-name
-Pool name.
-
-
-
-ping-interval
-Interval between pinging the server to show the client is alive, set in 
milliseconds. Pings are only sent when the ping-interval elapses between normal client messages. This must 
be set lower than the server’s maximum-time-between-pings.
-1 ms
-
-
-pr-single-hop-enabled
-Setting used for single-hop access to partitioned region data in the 
servers for some data operations. See PartitionResolver.
 See note in thread-local-connections 
below.
-True
-
-
-read-timeout
-Number of milliseconds to wait for a response from a server before the 
connection times out.
-1
-
-
-retry-attempts
-Number of times to retry an operation after a time-out or exception for 
high availability. If set to -1, the pool tries every available server once 
until it succeeds or has tried all servers.
--1
-
-
-server-group
-Server group from which to select connections. If not specified, the 
global group of all connected servers is used.
-empty
-
-
-socket-buffer-size
-Size of the socket buffer, in bytes, on each connection 
established.
-32768
-
-
-statistic-interval
-Default frequency, in milliseconds, with which the client statistics 
are sent to the server. A value of -1 indicates 
that the statistics are not sent to the server.
--1
-
-
-subscription-ack-interval
-Number of milliseconds to wait before sending an acknowledgment to the 
server about events received from the subscriptions.
-100
-
-
-subscription-enabled
-Whether to establish a server to client subscription.
-False
-
-
-subscription-message-tracking-timeout
-Number of milliseconds for which messages sent from a server to a 
client are tracked. The tracking is done to minimize duplicate events.
-9
-
-
-subscription-redundancy
-Redundancy for servers that contain subscriptions established by the 
client. A value of -1 causes all available 
servers in the specified group to be made redundant.
-0
-
-
-thread-local-connections
-Whether the connections must have affinity to the thread that last used 
them.
-
-**Note:**
-To set this to true, also set pr-single-hop-enabled to false. A true value in pr-single-hop-enabled automatically assigns a false value to thread-local-connections...
-
-False
-
-
-update-locator-list-interval
-An integer number of milliseconds defining the interval between locator 
list updates. If the value is less than or equal to 0, the update will be 
disabled.
-5000
-
-

[29/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/network_partition_scenario.svg
--
diff --git a/geode-docs/images_svg/network_partition_scenario.svg 
b/geode-docs/images_svg/network_partition_scenario.svg
deleted file mode 100644
index 89f7f48..000
--- a/geode-docs/images_svg/network_partition_scenario.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="58 313 508 353" 
width="508pt" height="353pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:13Zscenario 1Layer 1Network Partition Scenario  – Total weight of 111XSurviving SideM1 (weight=3)Locator  Membership 
CoordinatorM2(weight=15)Cache Server  Lead MemberM3 (weight=10)M4 (weight=10)M6 (weight=10)Cache ServerCache ServerCache ServerM5 
(weight=10)Cache Server- Detects membership weight loss of 47%- This 
distributed system stays upM7(weight=3)LocatorLosing SideM9 (weight=10)Cache Server
 M11 (weight=10)Cache ServerM10 (weight=10)Cache ServerM12 (weight=10)Cache ServerM8 (weight=10)Cache 
Server- Detects 
membership weight loss of 52%- 
Locator assumes coordinator role and shuts system down

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/p2p_topology.svg
--
diff --git a/geode-docs/images_svg/p2p_topology.svg 
b/geode-docs/images_svg/p2p_topology.svg
deleted file mode 100644
index 208fad3..000
--- a/geode-docs/images_svg/p2p_topology.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="59 293 499 121" 
width="499pt" height="121pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:03Zp2pLayer 1Application 
ProcessPeerApplication ProcessPeerApplication 
ProcessPeerCache DataCache DataCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/partitioned_data_HA.svg
--
diff --git a/geode-docs/images_svg/partitioned_data_HA.svg 
b/geode-docs/images_svg/partitioned_data_HA.svg
deleted file mode 100644
index cbb8b5b..000
--- a/geode-docs/images_svg/partitioned_data_HA.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 216 463 423" 
width="463pt" height="423pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:44ZHALayer 1stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="105.993164" y="14" textLength="84.006836">Member 
 >(M1)Partition Region 
Asecondary 
dataWXLogical 
ViewWXZYMember (M2)Partition Region Aprimary dataWXsecondary dataZYLogical ViewWXZYMember (M3)Partition Region 
Aprimary dataZYLogical ViewWXZYApplicationreadreadread

[35/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/client_server_message_tracking.svg
--
diff --git a/geode-docs/images_svg/client_server_message_tracking.svg 
b/geode-docs/images_svg/client_server_message_tracking.svg
deleted file mode 100644
index 69b0a55..000
--- a/geode-docs/images_svg/client_server_message_tracking.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="114 214 391 346" 
width="391pt" height="346pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:54Ztune-cs-messagingLayer 
1ServerBClient3A12A11B2A10A9B1send message A-10subscription queuethreadop #ServerBClient3A12A11B2A10B1subscription queuethreadop #Stage 1Stage 
2

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cluster-group-config.svg
--
diff --git a/geode-docs/images_svg/cluster-group-config.svg 
b/geode-docs/images_svg/cluster-group-config.svg
deleted file mode 100644
index 7977987..000
--- a/geode-docs/images_svg/cluster-group-config.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="86 108 489 320" 
width="489pt" height="320pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:52Z12 ColumnsLayer 1ClusterConfigurationfor 
entire clustercluster.xmlcluster.propertiesjarjarCluster 
Configurationfor group1group1.xmlgroup1.propertiesjarjarCluster Configurationfor group2group2.xmlgroup2.propertiesjarjar

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cluster_config_overview.svg
--
diff --git a/geode-docs/images_svg/cluster_config_overview.svg 
b/geode-docs/images_svg/cluster_config_overview.svg
deleted file mode 100644
index 93470e6..000
--- a/geode-docs/images_svg/cluster_config_overview.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="23 15 430 469" 
width="430pt" height="469pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-03-24 21:39Z12 ColumnsLayer 1Locator(s)ser
 ver34. New members request 
 the configuration from a 
locator.5. Locator 
distributes the configuration (including regions, disk-stores, jar 
files) to new servers joining the cluster.server2start 
locatorstart server1create disk-storecreate indexcreate 
regiondeploy...1. Developer/Administrator executes gfsh commands to 
configure the cluster.
 start 
server --name=server2start server 
--name=server3start server 
--name=server43. Developer/Administrator executes gfsh commands to add new members to the cluster.server4Layer 
2server12. gfsh saves the cluster configuration 
on the locator(s). Existing 
server(s) using cluster 
configuration service are 
configured.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/colocated_partitioned_regions.svg
--
diff --git a/geode-docs/images_svg/colocated_partitioned_regions.svg 
b/geode-docs/images_svg/colocated_partitioned_regions.svg
deleted file mode 100644
index 1cb609e..000
--- a/geode-docs/images_svg/colocated_partitioned_regions.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="90 285 383 221" 
width="383pt" height="221pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:09Zregion_data_colocationLayer 
1Member (M1)Partition Region AMember (M2)Partition Region 
Acustomer X datacustomer P dataPartition Region 
BPartition Region 
Bcustomer X 
datacustomer 
P 
data

[45/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/events/how_events_work.html.md.erb
--
diff --git a/geode-docs/developing/events/how_events_work.html.md.erb 
b/geode-docs/developing/events/how_events_work.html.md.erb
deleted file mode 100644
index 4553582..000
--- a/geode-docs/developing/events/how_events_work.html.md.erb
+++ /dev/null
@@ -1,94 +0,0 @@

-title:  How Events Work

-
-Members in your Geode distributed system receive cache updates from other 
members through cache events. The other members can be peers to the member, 
clients or servers or other distributed systems.
-
-## Events Features
-
-These are the primary features of Geode events:
-
--   Content-based events
--   Asynchronous event notifications with conflation
--   Synchronous event notifications for low latency
--   High availability through redundant messaging queues
--   Event ordering and once and only-once delivery
--   Distributed event notifications
--   Durable subscriptions
--   Continuous querying
-
-## Types of Events
-
-There are two categories of events and event handlers.
-
--   Cache events in the caching API are used by applications with a cache. 
Cache events provide detail-level notification for changes to your data. 
Continuous query events are in this category.
--   Administrative events in the administration API are used by administrative 
applications without caches.
-
-Both kinds of events can be generated by a single member operation.
-
-**Note:**
-You can handle one of these categories of events in a single system member. 
You cannot handle both cache and administrative events in a single member.
-
-Because Geode maintains the order of administrative events and the order of 
cache events separately, using cache events and administrative events in a 
single process can cause unexpected results.
-
-## Event Cycle
-
-The following steps describe the event cycle:
-
-1.  An operation begins, such as data put or a cache close.
-2.  The operation execution generates these objects:
--   An object of type `Operation` that describes the method that triggered 
the event.
--   An event object that describes the event, such as the member and 
region where the operation originated.
-
-3.  The event handlers that can handle the event are called and passed the 
event objects. Different event types require different handler types in 
different locations. If there is no matching event handler, that does not 
change the effect of the operation, which happens as usual.
-4.  When the handler receives the event, it triggers the handler’s callback 
method for this event. The callback method can hand off the event object as 
input to another method. Depending on the type of event handler, the callbacks 
can be triggered before or after the operation. The timing depends on the event 
handler, not on the event itself.
-**Note:**
-For transactions, after-operation listeners receive the events after the 
transaction has committed.
-
-5.  If the operation is distributed, so that it causes follow-on operations in 
other members, those operations generate their own events, which can be handled 
by their listeners in the same way.
-
-## Event Objects
-
-Event objects come in several types, depending on the operation. Some 
operations generate multiple objects of different types. All event objects 
contain data describing the event, and each event type carries slightly 
different kinds of data appropriate to its matching operation. An event object 
is stable. For example, its content does not change if you pass it off to a 
method on another thread.
-
-For cache events, the event object describes the operation performed in the 
local cache. If the event originated remotely, it describes the local 
application of the remote entry operation, not the remote operation itself. The 
only exception is when the local region has an empty data policy; then the 
event carries the information for the remote (originating) cache operation.
-
-## Event Distribution
-
-After a member processes an event in its local cache, it distributes it to 
remote caches according to the member's configuration and the configurations of 
the remote caches. For example, if a client updates its cache, the update is 
forwarded to the client's server. The server distributes the update to its 
peers and forwards it to any other clients according to their interest in the 
data entry. If the server system is part of a multi-site deployment and the 
data region is configured to use a gateway sender, then the gateway sender also 
forwards the update to a remote site, where the update is further distributed 
and propagated.
-
-## Event Handlers and Region Data Storage
-
-You can configure a region for no local data storage and still send and 
receive events for the region. Conversely, if you store data in the region, the 
cache is updated with 

[50/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/basic_config/data_regions/managing_data_regions.html.md.erb
--
diff --git 
a/geode-docs/basic_config/data_regions/managing_data_regions.html.md.erb 
b/geode-docs/basic_config/data_regions/managing_data_regions.html.md.erb
deleted file mode 100644
index cd9427b..000
--- a/geode-docs/basic_config/data_regions/managing_data_regions.html.md.erb
+++ /dev/null
@@ -1,205 +0,0 @@

-title:  Data Region Management

-
-Apache Geode provides different APIs and XML configuration models to support 
configuration and management of your data regions.
-
-
-You store your data in region entry key/value pairs, with keys and values 
being any object types your application needs.
-
-The `org.apache.geode.cache.Region` interface implements `java.util.Map`.
-
-Each region's attributes define how the data in the region is stored, 
distributed, and managed. Data regions can be distributed, partitioned among 
system members, or local to the member.
-
-You can create regions in the `cache.xml` file, by using the API, or with the 
gfsh command-line interface. You can use *region shortcuts* to configure 
commonly-used types of regions. For more information about region shortcuts, 
see [Region Shortcuts 
Reference](../../reference/topics/region_shortcuts_reference.html#reference_lt4_54c_lk).
-
-**Note:**
-If you change attributes that define a region, you must restart the member for 
the changes to take effect.
-
-## The Region APIs
-
-Geode's regions APIs provide specialized behavior for different system member 
types.
-
--   **Peer/Server Region APIs**. Use these methods, interfaces, and classes 
for peer/server region creation. These are in the `org.apache.geode.cache` 
package. They correspond to declarations in the `` element for creating 
and configuring regions.
--   **`org.apache.geode.cache.Cache.createRegionFactory`** . This method 
takes a `RegionShortcut` `enum` to initiate region configuration, and returns a 
`RegionFactory`. Use `createRegionFactory()`, not "`new 
RegionFactory`," to create a RegionFactory.
--   **`org.apache.geode.cache.RegionFactory`**. Provides methods to set 
individual region attributes and to create the region. The `create` call 
returns `Region`.
--   **`org.apache.geode.cache.RegionShortcut`**. Common region 
configurations can be retrieved through `Cache` `createRegionShortcut` and with 
the region attribute, `refid`.
--   **Client Region APIs**. Use these methods, interfaces, and classes for 
client region creation. These are in the `org.apache.geode.cache.client` 
package. They correspond to declarations in the `` element for 
creating and configuring regions.
-
-These are client versions of the Peer/Server Region APIs. These client 
APIs provide similar functionality, but are tailored to the needs and behaviors 
of client regions.
-
--   **`org.apache.geode.cache.clientCache.createRegionFactory`** . This 
method takes a `ClientRegionShortcut` `enum` to initiate region configuration, 
and returns a `ClientRegionFactory`.
--   **`org.apache.geode.cache.client.ClientRegionFactory`**. Provides 
methods to set individual region attributes and to create the region. The 
`create` call returns `Region`.
--   **`org.apache.geode.cache.client.ClientRegionShortcut`** . Common 
region configurations can be retrieved through `ClientCache` 
`createClientRegionFactory` and with the region attribute, `refid`.
--   **Region APIs Used For All Member Types**. These interfaces and classes 
are used universally for region management. These are in the 
`org.apache.geode.cache` package. They correspond to declarations under the 
`` and `` elements for creating and configuring regions.
--   **`org.apache.geode.cache.Region`** . Interface for managing your 
regions and their entries.
--   **`org.apache.geode.cache.RegionAttributes`** . Object holding region 
configuration settings.
--   **`org.apache.geode.cache.createRegionFactory`**. Can be used to 
create `RegionAttributes` to pass to `RegionFactory` and `ClientRegionFactory`.
-
-## Create and Access Data Regions
-
-Before you start, have your cache configuration defined, along with any 
cache-wide configuration your region requires, like disk store configuration 
and client server pool configuration.
-
-1.  Determine the region attributes requirements and identify the region 
shortcut setting that most closely matches your needs. See [Region Shortcuts 
and Custom Named Region Attributes](region_shortcuts.html) and [Region 
Shortcuts](../../reference/topics/chapter_overview_regionshortcuts.html) for 
more information.
-2.  Define any region attributes that are not provided in the shortcut you 
chose.
-3.  Create a region using any of the following methods:
--   `gfsh`. After starting up servers, a JMX manager and connecting to 

[49/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
--
diff --git 
a/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb 
b/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
deleted file mode 100644
index 51f89b0..000
--- 
a/geode-docs/configuring/cluster_config/gfsh_config_troubleshooting.html.md.erb
+++ /dev/null
@@ -1,58 +0,0 @@

-title:  Cluster Configuration Files and Troubleshooting

-
-When you use the cluster configuration service in Geode, you can examine the 
generated configuration files in the `cluster_config` directory on the locator. 
`gfsh` saves configuration files at the cluster-level and at the individual 
group-level.
-
-The following directories and configuration files are available on the locator 
running the cluster configuration service:
-
-**Cluster-level configuration**  
-For configurations that apply to all members of a cluster, the locator creates 
a `cluster` subdirectory within the `cluster_config` directory (or in the 
cluster configuration directory when starting up the locator with the 
`--cluster-config-dir=value` parameter) specified All servers receive this 
configuration when they are started using `gfsh`. This directory contains:
-
--   `cluster.xml` -- A Geode `cache.xml` file containing configuration common 
to all members
--   `cluster.properties` -- a Geode ` gemfire.properties` file containing 
properties common to all members
--   Jar files that are intended for deployment to all members
-
-
-
-**Group-level configuration**  
-When you specify the `--group` parameter in a `gfsh` command, (for example, 
`start server` or `create region`) the locator writes the configurations for 
each group in a subdirectory with the same name as the group. When you start a 
server that specifies one or more group names, the server receives both the 
cluster-level configurations and the configurations from all groups specified. 
This subdirectory contains:
-
--   `.xml` -- A Geode `cache.xml` file containing configurations 
common to all members of the group
--   `.properties` -- A Geode `gemfire.properties` file containing 
properties common to all members of the group
--   Jar files that are intended for deployment to all members of the group
-
-
-
-You can export a zip file that contains all artifacts of a cluster 
configuration. The zip file contains all of the files in the `cluster_config` 
(or otherwise specified) subdirectory of a locator. You can import this 
configuration to a new cluster. See [Exporting and Importing Cluster 
Configurations](export-import.html#concept_wft_dkq_34).
-
-## Individual Configuration Files and Cluster Configuration Files
-
-Geode applies the cluster-wide configuration files first and then group-level 
configurations next. If a member has its own configuration files defined 
(cache.xml and gemfire.properties files), those configurations are applied 
last. Whenever possible, use the member group-level configuration files in the 
cluster-configuration service to apply non-cluster-wide configurations on 
individual members.
-
-## Troubleshooting Tips
-
--   When you start a locator using `gfsh`, you should see the following 
message:
-
-``` pre
-Cluster configuration service is up and running.
-```
-
-If you do not see this message, there may be a problem with the cluster 
configuration service. Use the `status cluster-configuration-service` command 
to check the status of the cluster configuration.
-
--   If the command returns RUNNING, the cluster configuration is running 
normally.
--   If the command returns WAITING, run the `status locator` command. The 
output of this command returns the cause of the WAITING status.
--   If a server start fails with the following exception: 
`ClusterConfigurationNotAvailableException`, the cluster configuration service 
may not be in the RUNNING state. Because the server requests the cluster 
configuration from the locator, which is not available, the `start server` 
command fails.
--   You can determine what configurations a server received from a locator by 
examining the server's log file. See 
[Logging](../../managing/logging/logging.html#concept_30DB86B12B454E168B80BB5A71268865).
--   If a `start server` command specifies a cache.xml file that conflicts with 
the existing cluster configuration, the server startup may fail.
--   If a `gfsh` command fails because the cluster configuration cannot be 
saved, the following message displays:
-
-``` pre
-Failed to persist the configuration changes due to this command, 
-Revert the command to maintain consistency. Please use "status 
cluster-config-service" 
-to determine whether Cluster configuration service is RUNNING."
-```
-
--   There are some types of configurations that cannot be made 

[22/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/tune_cs_event_messaging.svg
--
diff --git a/geode-docs/images_svg/tune_cs_event_messaging.svg 
b/geode-docs/images_svg/tune_cs_event_messaging.svg
deleted file mode 100644
index 5af9f53..000
--- a/geode-docs/images_svg/tune_cs_event_messaging.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="114 214 391 346" 
width="391pt" height="346pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:33Ztune-cs-messagingLayer 
1ServerBClient3A12A11B2A10A9B1send message A-10subscription queuethreadop #
 ServerBClient3A
 12A11Bfont-family="Helvetica" font-size="10" font-weight="500" fill="black" 
 >x="9.719238" y="10" textLength="5.5615234">2y="468" width="27" height="18" fill="url(#Obj_Gradient_1b)"/>x="424.125" y="468" width="27" height="18" stroke="#252525" 
 >stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="9.165039" y="10" textLength="6.669922">Ax="451.125" y="468" width="27" height="18" 
 >fill="url(#Obj_Gradient_1c)"/>height="18" stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="6.9384766" y="10" textLength="11.123047">10B1subscription 
queuethreadop #Stage 1Stage 2

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/unbalanced_network_capacity_probs.svg
--
diff --git a/geode-docs/images_svg/unbalanced_network_capacity_probs.svg 
b/geode-docs/images_svg/unbalanced_network_capacity_probs.svg
deleted file mode 100644
index c24c082..000
--- a/geode-docs/images_svg/unbalanced_network_capacity_probs.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="113 275 283 271" 
width="283pt" height="271pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:58Zunbalanced networkLayer 
1app1(producer)app2app3app4networkswitch10 Mbps10 
Mbps10 Mbps5 Mbps

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
--
diff --git a/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb 
b/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
deleted file mode 100644
index 7303800..000
--- a/geode-docs/managing/autoreconnect/member-reconnect.html.md.erb
+++ /dev/null
@@ -1,42 +0,0 @@

-title:  Handling Forced Cache Disconnection Using Autoreconnect

-
-A Geode member may be forcibly disconnected from a Geode distributed system if 
the member is unresponsive for a period of time, or if a network partition 
separates one or more members into a group that is too small to act as the 
distributed system.
-
-## How the Autoreconnection Process Works
-
-After being disconnected from a distributed system a Geode member shuts down 
and then automatically restarts into a "reconnecting" state, while periodically 
attempting to rejoin the distributed system by contacting a list of known 
locators. If the member succeeds in reconnecting to a known locator, the member 
rebuilds its view of the distributed system from existing members and receives 
a new distributed system ID.
-
-If the member cannot connect to a known locator, the member will then check to 
see if it itself is a locator (or hosting an embedded locator process). If the 
member is a locator, then the member does a quorum-based reconnect; it will 
attempt to contact a quorum of the members that were in the membership view 
just before it became disconnected. If a quorum of members can be contacted, 
then startup of the distributed system is allowed to begin. Since the 
reconnecting member does not know which members survived the network partition 
event, all members that are in a reconnecting state will keep their UDP unicast 
ports open and respond to ping requests.
-
-Membership quorum is determined using the same member weighting system used in 
network partition detection. See [Membership Coordinators, Lead Members and 
Member 
Weighting](../network_partitioning/membership_coordinators_lead_members_and_weighting.html#concept_23C2606D59754106AFBFE17515DF4330).
-
-Note that when a locator is in the reconnecting state, it provides no 
discovery services for the distributed system.
-
-After the cache has reconnected, applications must fetch a reference to the 
new Cache, Regions, DistributedSystem and other artifacts. Old references will 
continue to throw cancellation exceptions 

[48/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/configuring/running/running_the_locator.html.md.erb
--
diff --git a/geode-docs/configuring/running/running_the_locator.html.md.erb 
b/geode-docs/configuring/running/running_the_locator.html.md.erb
deleted file mode 100644
index 64ac02e..000
--- a/geode-docs/configuring/running/running_the_locator.html.md.erb
+++ /dev/null
@@ -1,240 +0,0 @@

-title:  Running Geode Locator Processes

-
-The locator is a Geode process that tells new, connecting members where 
running members are located and provides load balancing for server use.
-
-
-You can run locators as peer locators, server locators, or both:
-
--   Peer locators give joining members connection information to members 
already running in the locator's distributed system.
--   Server locators give clients connection information to servers running in 
the locator's distributed system. Server locators also monitor server load and 
send clients to the least-loaded servers.
-
-By default, locators run as peer and server locators.
-
-You can run the locator standalone or embedded within another Geode process. 
Running your locators standalone provides the highest reliability and 
availability of the locator service as a whole.
-
-## Locator Configuration and Log Files
-
-Locator configuration and log files have the following properties:
-
--   When you start a standalone locator using `gfsh`, `gfsh` will 
automatically load the required JAR files 
(`$GEMFIRE/lib/locator-dependencies.jar`) into the CLASSPATH of the JVM 
process. If you start a standalone locator using the `LocatorLauncher` API, you 
must specify `$GEMFIRE/lib/locator-dependencies.jar` inside the command used to 
launch the locator process. For more information on CLASSPATH settings in 
Geode, see [CLASSPATH Settings for Geode 
Processes](../../getting_started/setup_classpath.html). You can modify the 
CLASSPATH by specifying the `--classpath` parameter.
--   Locators are members of the distributed system just like any other member. 
In terms of `mcast-port` and `locators` configuration, a locator should be 
configured in the same manner as a server. Therefore, if there are two other 
locators in the distributed system, each locator should reference the other 
locators (just like a server member would). For example:
-
-``` pre
-gfsh> start locator --name=locator1 --port=9009 --mcast-port=0 \
---locators='host1[9001],host2[9003]'
-```
-
--   You can configure locators within the `gemfire.properties` file or by 
specifying start-up parameters on the command line. If you are specifying the 
locator's configuration in a properties file, locators require the same 
`gemfire.properties` settings as other members of the distributed system and 
the same `gfsecurity.properties` settings if you are using a separate, 
restricted access security settings file.
-
-For example, to configure both locators and a multicast port in 
`gemfire.properties:`
-
-``` pre
-locators=host1[9001],host2[9003]
-mcast-port=0
-```
-
--   There is no cache configuration specific to locators.
--   For logging output, the locator creates a log file in its current working 
directory. Log file output defaults to `locator_name.log` in the locator's 
working directory. If you restart a locator with a previously used locator 
name, the existing *locator\_name*.log file is automatically renamed for you 
(for example, `locator1-01-01.log` or `locator1-02-01.log`). You can modify the 
level of logging details in this file by specifying a level in the 
`--log-level` argument when starting up the locator.
--   By default, a locator will start in a subdirectory (named after the 
locator) under the directory where `gfsh` is executed. This subdirectory is 
considered the current working directory. You can also specify a different 
working directory when starting the locator in `gfsh`.
--   By default, a locator that has been shutdown and disconnected due to a 
network partition event or member unresponsiveness will restart itself and 
automatically try to reconnect to the existing distributed system. When a 
locator is in the reconnecting state, it provides no discovery services for the 
distributed system. See [Handling Forced Cache Disconnection Using 
Autoreconnect](../../managing/autoreconnect/member-reconnect.html) for more 
details.
-
-## Locators and the Cluster Configuration Service
-
-Locators use the cluster configuration service to save configurations that 
apply to all cluster members, or to members of a specified group. The 
configurations are saved in the Locator's directory and are propagated to all 
locators in a distributed system. When you start servers using `gfsh`, the 
servers receive the group-level and cluster-level configurations from the 
locators.
-
-See [Overview of the Cluster Configuration 

[47/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/data_serialization/java_serialization.html.md.erb
--
diff --git 
a/geode-docs/developing/data_serialization/java_serialization.html.md.erb 
b/geode-docs/developing/data_serialization/java_serialization.html.md.erb
deleted file mode 100644
index 14b9ea3..000
--- a/geode-docs/developing/data_serialization/java_serialization.html.md.erb
+++ /dev/null
@@ -1,12 +0,0 @@

-title:  Standard Java Serialization

-
-You can use standard Java serialization for data you only distribute between 
Java applications. If you distribute your data between non-Java clients and 
Java servers, you need to do additional programming to get the data between the 
various class formats.
-
-
-Standard Java types are serializable by definition. For your domain classes, 
implement `java.io.Serializable`, then make sure to mark your transient and 
static variables as needed for your objects. For information, see the online 
documentation for `java.io.Serializable` for your Java version.
-
-Mixing `DataSerializable` with `Serializable` or `PdxSerializable` use on the 
same data can result in increased memory use and lower throughput than using 
just `Serializable` on the entire data, especially if the `Serializable` 
entries are in collections. The bigger the data collection, the lower the 
throughput as the metadata for the collection entries is not shared when using 
`DataSerializable`.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
--
diff --git 
a/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
 
b/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
deleted file mode 100644
index 59ceb3c..000
--- 
a/geode-docs/developing/data_serialization/jsonformatter_pdxinstances.html.md.erb
+++ /dev/null
@@ -1,29 +0,0 @@

-title:  Adding JSON Documents to the Geode Cache

-
-The `JSONFormatter` API allows you to put JSON formatted documents into 
regions and retrieve them later by storing the documents internally as 
PdxInstances.
-
-Geode now supports the use of JSON formatted documents natively. When you add 
a JSON document to a Geode cache, you call the JSONFormatter APIs to transform 
them into the PDX format (as a `PdxInstance`), which enables Geode to 
understand the JSON document at a field level.
-
-In terms of querying and indexing, because the documents are stored internally 
as PDX, applications can index on any field contained inside the JSON document 
including any nested field (within JSON objects or JSON arrays.) Any queries 
run on these stored documents will return PdxInstances as results. To update a 
JSON document stored in Geode , you can execute a function on the PdxInstance.
-
-You can then use the `JSONFormatter` to convert the PdxInstance results back 
into the JSON document.
-
-`JSONFormatter` uses a streaming parser 
([Jackson](http://wiki.fasterxml.com/JacksonHome), JSON processor) to turn JSON 
documents into the optimized PDX format. To use the JSONFormatter, make sure 
that `$GEMFIRE/lib/server-dependencies.jar` is available in your application's 
CLASSPATH.
-
-The `JSONFormatter` class has four static methods that are used to convert 
JSON document into PdxInstances and then to convert those PdxInstances back 
into JSON document.
-
-You need to call the following methods before putting any JSON document into 
the Geode region:
-
--   `fromJSON`. Creates a PdxInstance from a JSON byte array. Returns the 
PdxInstance.
--   `fromJSON`. Creates a PdxInstance from a JSON string. Returns the 
PdxInstance.
-
-After putting the JSON document into a region as a PdxInstance, you can 
execute standard Geode queries and create indexes on the JSON document in the 
same manner you would query or index any other Geode PdxInstance.
-
-After executing a Geode query or calling `region.get`, you can use the 
following methods to convert a PdxInstance back into the JSON format:
-
--   `toJSON`. Reads a PdxInstance and returns a JSON string.
--   `toJSONByteArray`. Reads a PdxInstance and returns a JSON byte array.
-
-For more information on using the JSONFormatter, see the Java API 
documentation for `org.apache.geode.pdx.JSONFormatter`.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/data_serialization/persist_pdx_metadata_to_disk.html.md.erb
--
diff --git 
a/geode-docs/developing/data_serialization/persist_pdx_metadata_to_disk.html.md.erb
 
b/geode-docs/developing/data_serialization/persist_pdx_metadata_to_disk.html.md.erb
deleted file mode 100644
index 37b11fc..000
--- 

[51/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

GEODE-1964: native client documentation (note: contains references to images in 
the geode-docs directories)


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

Branch: refs/heads/feature/GEODE-1964
Commit: ff80a9315ae63feb2b0b72a546dc6d36e7ed6dc3
Parents: ccc2fbd
Author: Dave Barnes 
Authored: Tue Oct 4 17:09:35 2016 -0700
Committer: Dave Barnes 
Committed: Tue Oct 4 17:09:35 2016 -0700

--
 geode-docs/.gitignore   |6 -
 geode-docs/CONTRIBUTE.md|   63 -
 geode-docs/README.md|   93 -
 geode-docs/about_geode.html.md.erb  |9 -
 geode-docs/basic_config/book_intro.html.md.erb  |   23 -
 .../chapter_overview.html.md.erb|   23 -
 ...uted_system_member_configuration.html.md.erb |   34 -
 .../config_concepts/local_vs_remote.html.md.erb |   12 -
 .../chapter_overview.html.md.erb|   15 -
 .../managing_data_entries.html.md.erb   |  129 -
 .../using_custom_classes.html.md.erb|   34 -
 .../data_regions/chapter_overview.html.md.erb   |   48 -
 .../create_a_region_with_API.html.md.erb|   63 -
 .../create_a_region_with_cacheXML.html.md.erb   |   68 -
 .../create_a_region_with_gfsh.html.md.erb   |   38 -
 .../creating_custom_attributes.html.md.erb  |   47 -
 .../managing_data_regions.html.md.erb   |  205 --
 .../managing_region_attributes.html.md.erb  |   96 -
 .../new_region_existing_data.html.md.erb|   11 -
 .../data_regions/region_naming.html.md.erb  |   14 -
 .../data_regions/region_shortcuts.html.md.erb   |   98 -
 .../store_retrieve_region_shortcuts.html.md.erb |   60 -
 .../setting_distributed_properties.html.md.erb  |   64 -
 .../the_cache/chapter_overview.html.md.erb  |   31 -
 .../intro_cache_management.html.md.erb  |   79 -
 .../managing_a_client_cache.html.md.erb |   67 -
 .../managing_a_multiuser_cache.html.md.erb  |   49 -
 .../managing_a_peer_server_cache.html.md.erb|   64 -
 .../managing_a_secure_cache.html.md.erb |   50 -
 .../setting_cache_initializer.html.md.erb   |   59 -
 .../setting_cache_properties.html.md.erb|   22 -
 .../configuring/chapter_overview.html.md.erb|   67 -
 .../deploying_application_jars.html.md.erb  |  114 -
 .../cluster_config/export-import.html.md.erb|   39 -
 .../gfsh_config_troubleshooting.html.md.erb |   58 -
 .../gfsh_load_from_shared_dir.html.md.erb   |   27 -
 .../cluster_config/gfsh_persist.html.md.erb |  108 -
 .../cluster_config/gfsh_remote.html.md.erb  |   61 -
 .../persisting_configurations.html.md.erb   |  320 --
 .../using_member_groups.html.md.erb |   27 -
 .../running/change_file_spec.html.md.erb|   40 -
 .../running/default_file_specs.html.md.erb  |   59 -
 .../deploy_config_files_intro.html.md.erb   |   17 -
 .../running/deploying_config_files.html.md.erb  |   28 -
 .../deploying_config_jar_files.html.md.erb  |   35 -
 .../running/firewall_ports_config.html.md.erb   |   15 -
 .../running/firewalls_connections.html.md.erb   |   18 -
 .../running/firewalls_multisite.html.md.erb |   70 -
 .../running/firewalls_ports.html.md.erb |  229 --
 .../running/managing_output_files.html.md.erb   |   16 -
 .../running/running_the_cacheserver.html.md.erb |  182 -
 .../running/running_the_locator.html.md.erb |  240 --
 .../starting_up_shutting_down.html.md.erb   |  129 -
 geode-docs/developing/book_intro.html.md.erb|   57 -
 .../chapter_overview.html.md.erb|   21 -
 .../continuous_querying_whats_next.html.md.erb  |   71 -
 .../how_continuous_querying_works.html.md.erb   |   81 -
 ...implementing_continuous_querying.html.md.erb |  185 -
 .../PDX_Serialization_Features.html.md.erb  |   23 -
 .../auto_serialization.html.md.erb  |  124 -
 ...ation_with_class_pattern_strings.html.md.erb |   68 -
 .../chapter_overview.html.md.erb|   23 -
 .../data_serialization_options.html.md.erb  |   51 -
 .../extending_the_autoserializer.html.md.erb|  106 -
 .../gemfire_data_serialization.html.md.erb  |   35 -
 .../gemfire_pdx_serialization.html.md.erb   |   47 -
 .../java_serialization.html.md.erb  |   12 -
 .../jsonformatter_pdxinstances.html.md.erb  |   29 -
 .../persist_pdx_metadata_to_disk.html.md.erb|   36 -
 .../program_application_for_pdx.html.md.erb |   90 -
 .../use_pdx_high_level_steps.html.md.erb|   32 -
 .../use_pdx_serializable.html.md.erb|   98 -
 .../use_pdx_serializer.html.md.erb  |  128 -
 

[33/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/custom_partitioned.svg
--
diff --git a/geode-docs/images_svg/custom_partitioned.svg 
b/geode-docs/images_svg/custom_partitioned.svg
deleted file mode 100644
index e952a5c..000
--- a/geode-docs/images_svg/custom_partitioned.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="102 228 392 186" 
width="392pt" height="186pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:07Zcustom_partitioningLayer 
1Member (M1)Partition Region AMember (M2)Partition Region 
Acustomer X 
datacustomer Y datacustomer 
P 
datacustomer Q 
data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/developing_overflow.svg
--
diff --git a/geode-docs/images_svg/developing_overflow.svg 
b/geode-docs/images_svg/developing_overflow.svg
deleted file mode 100644
index f5cf3bb..000
--- a/geode-docs/images_svg/developing_overflow.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="77 330 414 138" 
width="414pt" height="138pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:42ZoverflowLayer 1MemberXYZXRegion BDisk 
Filesvalues for 
overflow 
entriesoffload overflowupdate/invalidate/destroysatisfy get<
 /svg>

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/developing_persistence.svg
--
diff --git a/geode-docs/images_svg/developing_persistence.svg 
b/geode-docs/images_svg/developing_persistence.svg
deleted file mode 100644
index e5f3174..000
--- a/geode-docs/images_svg/developing_persistence.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="113 479 415 133" 
width="415pt" height="133pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:40ZpersistenceLayer 1MemberXYZXYZRegion Apersist values from createDisk Fileskeys and 
values for all entriesupdate/invalidate/destroy

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/developing_persistence_and_overflow.svg
--
diff --git a/geode-docs/images_svg/developing_persistence_and_overflow.svg 
b/geode-docs/images_svg/developing_persistence_and_overflow.svg
deleted file mode 100644
index c09ce8e..000
--- a/geode-docs/images_svg/developing_persistence_and_overflow.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 330 416 139" 
width="416pt" height="139pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:47Zpersist+overflowLayer 
1GemFire MemberXYZXYZRegion 
CDisk Fileskeys and values for all 
entriespersist values from createupdate/invalidate/destroysatisfy get

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/distributed_how_1.svg
--
diff --git a/geode-docs/images_svg/distributed_how_1.svg 
b/geode-docs/images_svg/distributed_how_1.svg
deleted file mode 100644
index 4c4026a..000
--- a/geode-docs/images_svg/distributed_how_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:12Zhow_it_works-1Layer 
1 Member (M1)Member (M2)X1ApplicationDistributed Region AXDistributed Region 
AX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/distributed_how_2.svg
--
diff --git a/geode-docs/images_svg/distributed_how_2.svg 
b/geode-docs/images_svg/distributed_how_2.svg
deleted file mode 100644
index ccc6874..000
--- a/geode-docs/images_svg/distributed_how_2.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="131 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 

[43/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb 
b/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb
deleted file mode 100644
index 5082cc4..000
--- a/geode-docs/developing/partitioned_regions/how_pr_ha_works.html.md.erb
+++ /dev/null
@@ -1,44 +0,0 @@

-title:  Understanding High Availability for Partitioned Regions

-
-With high availability, each member that hosts data for the partitioned region 
gets some primary copies and some redundant (secondary) copies.
-
-
-
-With redundancy, if one member fails, operations continue on the partitioned 
region with no interruption of service:
-
--   If the member hosting the primary copy is lost, Geode makes a secondary 
copy the primary. This might cause a temporary loss of redundancy, but not a 
loss of data.
--   Whenever there are not enough secondary copies to satisfy redundancy, the 
system works to recover redundancy by assigning another member as secondary and 
copying the data to it.
-
-**Note:**
-You can still lose cached data when you are using redundancy if enough members 
go down in a short enough time span.
-
-You can configure how the system works to recover redundancy when it is not 
satisfied. You can configure recovery to take place immediately or, if you want 
to give replacement members a chance to start up, you can configure a wait 
period. Redundancy recovery is also automatically attempted during any 
partitioned data rebalancing operation. Use the 
`gemfire.MAX_PARALLEL_BUCKET_RECOVERIES` system property to configure the 
maximum number of buckets that are recovered in parallel. By default, up to 8 
buckets are recovered in parallel any time the system attempts to recover 
redundancy.
-
-Without redundancy, the loss of any of the region's data stores causes the 
loss of some of the region's cached data. Generally, you should not use 
redundancy when your applications can directly read from another data source, 
or when write performance is more important than read performance.
-
-## Controlling Where Your Primaries and Secondaries 
Reside
-
-By default, Geode places your primary and secondary data copies for you, 
avoiding placement of two copies on the same physical machine. If there are not 
enough machines to keep different copies separate, Geode places copies on the 
same physical machine. You can change this behavior, so Geode only places 
copies on separate machines.
-
-You can also control which members store your primary and secondary data 
copies. Geode provides two options:
-
--   **Fixed custom partitioning**. This option is set for the region. Fixed 
partitioning gives you absolute control over where your region data is hosted. 
With fixed partitioning, you provide Geode with the code that specifies the 
bucket and data store for each data entry in the region. When you use this 
option with redundancy, you specify the primary and secondary data stores. 
Fixed partitioning does not participate in rebalancing because all bucket 
locations are fixed by you.
--   **Redundancy zones**. This option is set at the member level. Redundancy 
zones let you separate primary and secondary copies by member groups, or zones. 
You assign each data host to a zone. Then Geode places redundant copies in 
different redundancy zones, the same as it places redundant copies on different 
physical machines. You can use this to split data copies across different 
machine racks or networks, This option allows you to add members on the fly and 
use rebalancing to redistribute the data load, with redundant data maintained 
in separate zones. When you use redundancy zones, Geode will not place two 
copies of the data in the same zone, so make sure you have enough zones.
-
-## Running Processes in Virtual Machines
-
-By default, Geode stores redundant copies on different machines. When you run 
your processes in virtual machines, the normal view of the machine becomes the 
VM and not the physical machine. If you run multiple VMs on the same physical 
machine, you could end up storing partitioned region primary buckets in 
separate VMs, but on the same physical machine as your secondaries. If the 
physical machine fails, you can lose data. When you run in VMs, you can 
configure Geode to identify the physical machine and store redundant copies on 
different physical machines.
-
-## Reads and Writes in Highly-Available Partitioned 
Regions
-
-Geode treats reads and writes differently in highly-available partitioned 
regions than in other regions because the data is available in multiple members:
-
--   Write operations (like `put` and `create`) go to the primary for the data 
keys and then are distributed synchronously to the redundant copies. Events are 
sent to the members configured 

[36/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cache_data_loader.svg
--
diff --git a/geode-docs/images_svg/cache_data_loader.svg 
b/geode-docs/images_svg/cache_data_loader.svg
deleted file mode 100644
index 0493df6..000
--- a/geode-docs/images_svg/cache_data_loader.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="113 230 427 229" 
width="427pt" height="229pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:40Zdata-loadersLayer 1databaseMember (M2)Partitioned Region AYCache LoaderMember (M1)Partitioned Region AXCache 
LoaderMember (M3)Partitioned Region AZCache Loader

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cache_data_loader_2.svg
--
diff --git a/geode-docs/images_svg/cache_data_loader_2.svg 
b/geode-docs/images_svg/cache_data_loader_2.svg
deleted file mode 100644
index 7334890..000
--- a/geode-docs/images_svg/cache_data_loader_2.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 275 427 229" 
width="427pt" height="229pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:41Zdata-loaders-2Layer 
1databaseMember (M2)Distributed Region AXMember (M1)Distributed Region AXCache 
LoaderMember (M3)Distributed Region AX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/client_server_deployment.svg
--
diff --git a/geode-docs/images_svg/client_server_deployment.svg 
b/geode-docs/images_svg/client_server_deployment.svg
deleted file mode 100644
index dbaff91..000
--- a/geode-docs/images_svg/client_server_deployment.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="99 332 374 297" 
width="374pt" height="297pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:01ZcsLayer 1filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>ServerClientLocal Cacheconnection 
poolServer 
FarmLocatorsend address 
and load information to locatorCache Clientsrequest server information from 
locator,locator responds with least loaded serversend, receive cache datareceive server eventsCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/client_server_event_dist.svg
--
diff --git a/geode-docs/images_svg/client_server_event_dist.svg 
b/geode-docs/images_svg/client_server_event_dist.svg
deleted file mode 100644
index e19e46a..000
--- a/geode-docs/images_svg/client_server_event_dist.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="66 203 487 337" 
width="487pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:51Zcs-event-distribution-2Layer 
1Distributed SystemClie
 nt 1Region Apool-name = ServerPoolServerRegion AXClient 2XRegion Apool-name = ServerPoolpool “ServerPool”(with or without subscriptions 
enabled)pool 
“ServerPool”(with 
subscriptions enabled,interest register in X,receiveValues = 
true)Update/CreateXXsubscription12334

[25/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/transactions_partitioned_2.svg
--
diff --git a/geode-docs/images_svg/transactions_partitioned_2.svg 
b/geode-docs/images_svg/transactions_partitioned_2.svg
deleted file mode 100644
index a9445e1..000
--- a/geode-docs/images_svg/transactions_partitioned_2.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="36 167 580 274" 
width="580pt" height="274pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:52Zpartition-2Layer 1Member 
(M1)CachePartition Region 
AJava Applicationsecondary dataWMember (M2)
 CacheT3XPartition Region Bdata accessor 
onlyReplicate Region RFGPartition Region 
Aprimary 
dataWXPartition Region 
Bprimary 
dataZReplicate Region RFGYRegion AWXRegion BZRegion 
RFG
 YTransaction T3

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/transactions_replicate_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_1.svg 
b/geode-docs/images_svg/transactions_replicate_1.svg
deleted file mode 100644
index 094bc58..000
--- a/geode-docs/images_svg/transactions_replicate_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="36 149 585 337" 
width="585pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:54Zreplicate-1Layer 1Member (M1)CacheReplicate Region A
 Java ApplicationWMember 
(M2)T1Replicate Region BXRegion AW1Region BX1Transaction T1CacheReplicate Region AWMember 
(M3)CacheReplicate Region BX2Replicate Region BXTransaction T2Java ApplicationT2

[02/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
deleted file mode 100644
index 9864fb2..000
--- a/geode-docs/tools_modules/gfsh/command-pages/create.html.md.erb
+++ /dev/null
@@ -1,937 +0,0 @@

-title: create

-
-
-
-Create async-event-queues, disk-stores, gateway receivers, gateway senders, 
indexes, and regions.
-
--   **[create 
async-event-queue](../../../tools_modules/gfsh/command-pages/create.html#topic_ryz_pb1_dk)**
-
-Creates an asynchronous event queue for batching events before they are 
delivered by a gateway sender.
-
--   **[create defined 
indexes](../../../tools_modules/gfsh/command-pages/create.html#topic_w2t_l3m_qq)**
-
-Creates all the defined indexes.
-
--   **[create 
disk-store](../../../tools_modules/gfsh/command-pages/create.html#topic_bkn_zty_ck)**
-
-Defines a pool of one or more disk stores, which can be used by regions 
and client subscription queues, and gateway sender queues for WAN distribution.
-
--   **[create 
gateway-receiver](../../../tools_modules/gfsh/command-pages/create.html#topic_a4x_pb1_dk)**
-
-Creates a gateway receiver. You can only have one gateway receiver on each 
member, and unlike a gateway sender, you do not need to specify an identifier 
for the gateway receiver .
-
--   **[create 
gateway-sender](../../../tools_modules/gfsh/command-pages/create.html#topic_hg2_bjz_ck)**
-
-Creates a gateway sender on one or more members of a distributed system.
-
--   **[create 
index](../../../tools_modules/gfsh/command-pages/create.html#topic_960A5B6FD3D84E1881EE118E299DD12D)**
-
-Create an index that can be used when executing queries.
-
--   **[create 
region](../../../tools_modules/gfsh/command-pages/create.html#topic_54B0985FEC5241CA9D26B0CE0A5EA863)**
-
-Create a region with given path and configuration.
-
-## create async-event-queue
-
-Creates an asynchronous event queue for batching events before they are 
delivered by a gateway sender.
-
-See [Configuring Multi-Site (WAN) Event 
Queues](../../../developing/events/configure_multisite_event_messaging.html#configure_multisite_event_messaging).
-
-**Availability:** Online. You must be connected in `gfsh` to a JMX Manager 
member to use this command.
-
-**Syntax:**
-
-``` pre
-create async-event-queue --id=value --listener=value 
[--group=value(nullvalue)*]
-[--parallel(=value)?] [--enable-batch-conflation(=value)?] 
[--batch-size=value]
-[--batch-time-interval=value] [--persistent(=value)?] [--disk-store=value]
-[--disk-synchronous(=value)?] [--max-queue-memory=value]
-[--dispatcher-threads=value] [--order-policy=value]
-[--gateway-event-filter=value(,value)*]
-[--gateway-event-substitution-filter=value] 
-[--listener-param=value(,value)*]
-```
-
-
-
-
-Table 1. Create Async-Event-Queue 
Parameters
-
-
-
-
-
-
-
-Name
-Description
-Default Value
-
-
-
-
-\-\-id
-Required. ID of the asynchronous event queue
- 
-
-
-\-\-group
-The queue is created on all members of this group. If you do not specify a 
group the queue is created on all members.
- 
-
-
-\-\-parallel
-Specifies whether the queue is parallel.
-false
-
-
-\-\-enable-batch-conflation
-Enables batch conflation.
-false
-
-
-\-\-batch-size
-Maximum number of messages that a batch can contain.
-100
-
-
-\-\-batch-time-interval
-Maximum amount of time, in ms, that can elapse before a batch is 
delivered.
-5
-
-
-\-\-persistent
-Boolean value that determines whether Geode persists this queue.
-false
-If specified with out a value, default is true.
-
-
-\-\-disk-store
-Named disk store to use for storing queue overflow, or for persisting the 
queue. If you specify a value, the named disk store must exist. If you specify 
a null value, Geode uses the default disk store for overflow and queue 
persistence.
- 
-
-
-\-\-disk-synchronous
-Specifies whether disk writes are synchronous.
-true
-
-
-\-\-max-queue-memory
-Maximum amount of memory in megabytes that the queue can consume before 
overflowing to disk.
-100
-
-
-\-\-dispatcher-threads
-Number of threads used for sending events.
-5
-
-
-\-\-order-policy
-Policy for dispatching events when \-\-dispatcher-threads is  1. 
Possible values are THREAD, KEY, PARTITION.
-KEY
-
-
-\-\-gateway-event-filter
-List of fully qualified class names of GatewayEventFilters for this queue. 
These classes filter events before dispatching to remote servers.
- 
-
-
-\-\-gateway-event-substitution-filter
-Fully-qualified class name of the GatewayEventSubstitutionFilter for this queue.
- 
-
-
-\-\-listener
-Required. Fully-qualified class name of Async Event Listener for 
this queue
- 
-
-
-\-\-listener-param
-Parameter name and value to be passed to the Async Event 

[44/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/expiration/configuring_data_expiration.html.md.erb
--
diff --git 
a/geode-docs/developing/expiration/configuring_data_expiration.html.md.erb 
b/geode-docs/developing/expiration/configuring_data_expiration.html.md.erb
deleted file mode 100644
index 0fae74a..000
--- a/geode-docs/developing/expiration/configuring_data_expiration.html.md.erb
+++ /dev/null
@@ -1,66 +0,0 @@

-title:  Configure Data Expiration

-
-Configure the type of expiration and the expiration action to use.
-
-
-
--   Set the region's `statistics-enabled` attribute to true.
-
-The statistics used for expiration are available directly to the 
application through the `CacheStatistics` object returned by the `Region` and 
`Region.Entry` `getStatistics` methods. The `CacheStatistics` object also 
provides a method for resetting the statistics counters.
-
--   Set the expiration attributes by expiration type, with the max times and 
expiration actions. See the region attributes listings for 
`entry-time-to-live`, `entry-idle-time`, `region-time-to-live`, and 
`region-idle-time` in 
[region-attributes](../../reference/topics/cache_xml.html#region-attributes).
-
-For partitioned regions, to ensure reliable read behavior, use the 
`time-to-live` attributes, not the `idle-time` attributes. In addition, you 
cannot use `local-destroy` or `local-invalidate` expiration actions in 
partitioned regions.
-
-Replicated regions example:
-
-``` pre
-// Setting standard expiration on an entry
- 
-   
- 
-   
- 
-```
-
--   Override the region-wide settings for specific entries, if required by 
your application. To do this:
-1.  Program a custom expiration class that implements 
`org.apache.geode.cache.CustomExpiry`. Example:
-
-``` pre
-// Custom expiration class
-// Use the key for a region entry to set entry-specific expiration 
timeouts of 
-//   10 seconds for even-numbered keys with a DESTROY action on the 
expired entries
-//   Leave the default region setting for all odd-numbered keys. 
-public class MyClass implements CustomExpiry, Declarable 
-{ 
-private static final ExpirationAttributes CUSTOM_EXPIRY = 
-new ExpirationAttributes(10, ExpirationAction.DESTROY); 
-public ExpirationAttributes getExpiry(Entry entry) 
-{ 
-int key = (Integer)entry.getKey(); 
-return key % 2 == 0 ? CUSTOM_EXPIRY : null; 
-}
-}
-```
-2.  Define the class inside the expiration attributes settings for the 
region. Example:
-
-
-``` pre
- 
-
- 
- 
- 
- 
-com.company.mypackage.MyClass 
- 
- 
- 
-
-```
-
-You can also configure Regions using the gfsh command-line interface, however, 
you cannot configure `custom-expiry` using gfsh. See [Region 
Commands](../../tools_modules/gfsh/quick_ref_commands_by_area.html#topic_EF03119A40EE492984F3B6248596E1DD).
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/expiration/how_expiration_works.html.md.erb
--
diff --git a/geode-docs/developing/expiration/how_expiration_works.html.md.erb 
b/geode-docs/developing/expiration/how_expiration_works.html.md.erb
deleted file mode 100644
index 5c3be02..000
--- a/geode-docs/developing/expiration/how_expiration_works.html.md.erb
+++ /dev/null
@@ -1,53 +0,0 @@

-title:  How Expiration Works

-
-Expiration removes old entries and entries that you are not using. You can 
destroy or invalidate entries.
-
-
-Expiration activities in distributed regions can be distributed or local. 
Thus, one cache could control expiration for a number of caches in the system.
-
-This figure shows two basic expiration settings for a producer/consumer 
system. The producer member (on the right) populates the region from a database 
and the data is automatically distributed throughout the system. The data is 
valid only for one hour, so the producer performs a distributed destroy on 
entries that are an hour old. The other applications are consumers. The 
consumers free up space in their caches by removing their local copies of the 
entries for which there is no local interest (idle-time expiration). Requests 
for entries that have expired on the consumers will be forwarded to the 
producer.
-
-
-
-## Expiration Types
-
-Apache Geode uses the following expiration types:
-
--   **Time to live (TTL)**. The amount of time, in seconds, the object may 
remain in the cache after the last creation or update. For entries, the counter 
is set to zero for 

[31/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/hibernate_cs.svg
--
diff --git a/geode-docs/images_svg/hibernate_cs.svg 
b/geode-docs/images_svg/hibernate_cs.svg
deleted file mode 100644
index ce9c3a8..000
--- a/geode-docs/images_svg/hibernate_cs.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="59 233 493 205" 
width="493pt" height="205pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:24ZcsLayer 
1Partitioned Session DataPartitioned Session DataPartitioned 
Session 
DataServerServerServerPartitioned DataHibernate 
SessionClientaccess to Hibernate entitiesconnection poolIf data not found in cache, Hibernate accesses database...RelationalDatabasePartitioned DataPartitioned Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/hibernate_overview.svg
--
diff --git a/geode-docs/images_svg/hibernate_overview.svg 
b/geode-docs/images_svg/hibernate_overview.svg
deleted file mode 100644
index 0fd8669..000
--- a/geode-docs/images_svg/hibernate_overview.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="146 287 389 228" 
width="389pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:06ZoverviewLayer 1Cached DataCached DataMemberHibernate 
SessionMemberCached Dataaccess to Hibernate entitiesIf data not found in cache, Hibernate accesses 
database...RelationalDatabaseCached Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/hibernate_p2p.svg
--
diff --git a/geode-docs/images_svg/hibernate_p2p.svg 
b/geode-docs/images_svg/hibernate_p2p.svg
deleted file mode 100644
index bc536dc..000
--- a/geode-docs/images_svg/hibernate_p2p.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="59 269 499 228" 
width="499pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:09Zp2pLayer 1stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="27.143066" y="10" textLength="81.713867">Hibernate 
 >SessionPeer CacheHibernate 
SessionPeer CacheHibernate SessionPeer CacheReplicated DataReplicated DataReplicated
  Dataaccess 
to Hibernate entitiesaccess to Hibernate entitiesaccess to Hibernate entitiesIf data not found in cache, Hibernate accesses 
database...RelationalDatabase

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/how_partitioning_works_1.svg
--
diff --git a/geode-docs/images_svg/how_partitioning_works_1.svg 
b/geode-docs/images_svg/how_partitioning_works_1.svg
deleted file mode 100644
index b7cd2a2..000
--- a/geode-docs/images_svg/how_partitioning_works_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="181 308 386 413" 
width="386pt" height="413pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:44Zhow_it_works_1Layer 
1Partitioned Region ALogical ViewXYZPartitioned Region APhysical ViewXMachine 1P
 artitioned Region AYMachine 2Partitioned Region AZMachine 3

[15/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
--
diff --git 
a/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
 
b/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
deleted file mode 100644
index 50f97b6..000
--- 
a/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
+++ /dev/null
@@ -1,75 +0,0 @@

-title:  Producing Artifacts for Troubleshooting

-
-There are several types of files that are critical for troubleshooting.
-
-Geode logs and statistics are the two most important artifacts used in 
troubleshooting. In addition, they are required for Geode system health 
verification and performance analysis. For these reasons, logging and 
statistics should always be enabled, especially in production. Save the 
following files for troubleshooting purposes:
-
--   Log files. Even at the default logging level, the log contains data that 
may be important. Save the whole log, not just the stack. For comparison, save 
log files from before, during, and after the problem occurred.
--   Statistics archive files.
--   Core files or stack traces.
--   For Linux, you can use gdb to extract a stack from a core file.
--   Crash dumps.
--   For Windows, save the user mode dump files. Some locations to check for 
these files:
--   C:\\ProgramData\\Microsoft\\Windows\\WER\\ReportArchive
--   C:\\ProgramData\\Microsoft\\Windows\\WER\\ReportQueue
--   
C:\\Users\\*UserProfileName*\\AppData\\Local\\Microsoft\\Windows\\WER\\ReportArchive
--   
C:\\Users\\*UserProfileName*\\AppData\\Local\\Microsoft\\Windows\\WER\\ReportQueue
-
-When a problem arises that involves more than one process, a network problem 
is the most likely cause. When you diagnose a problem, create a log file for 
each member of all the distributed systems involved. If you are running a 
client/server architecture, create log files for the clients.
-
-**Note:**
-You must run a time synchronization service on all hosts for troubleshooting. 
Synchronized time stamps ensure that log messages on different hosts can be 
merged to accurately reproduce a chronological history of a distributed run.
-
-For each process, complete these steps:
-
-1.  Make sure the host’s clock is synchronized with the other hosts. Use a 
time synchronization tool such as Network Time Protocol (NTP).
-2.  Enable logging to a file instead of standard output by editing 
`gemfire.properties` to include this line:
-
-``` pre
-log-file=filename
-```
-
-3.  Keep the log level at `config` to avoid filling up the disk while 
including configuration information. Add this line to `gemfire.properties`:
-
-``` pre
-log-level=config
-```
-
-**Note:**
-Running with the log level at `fine` can impact system performance and 
fill up your disk.
-
-4.  Enable statistics gathering for the distributed system either by modifying 
`gemfire.properties`:
-
-``` pre
-statistic-sampling-enabled=true
-statistic-archive-file=StatisticsArchiveFile.gfs
-```
-
-or by using the `gfsh alter rutime` command:
-
-``` pre
-alter runtime --group=myMemberGroup --enable-statistics=true 
--statistic-archive-file=StatisticsArchiveFile.gfs
-```
-
-**Note:**
-Collecting statistics at the default sample rate frequency of 1000 
milliseconds does not incur performance overhead.
-
-5.  Run the application again.
-6.  Examine the log files. To get the clearest picture, merge the files. To 
find all the errors in the log file, search for lines that begin with these 
strings:
-
-``` pre
-[error
-[severe
-```
-
-For details on merging log files, see the `--merge-log` argument for the 
[export 
logs](../../tools_modules/gfsh/command-pages/export.html#topic_B80978CC659244AE91E2B8CE56EBDFE3)command.
-
-7.  Export and analyze the stack traces on the member or member group where 
the application is running. Use the `gfsh export stack-traces   
  command`. For example:
-
-``` pre
-gfsh> export stack-traces --file=ApplicationStackTrace.txt --member=member1
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
--
diff --git 
a/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
 
b/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
deleted file mode 100644
index 6c65227..000
--- 
a/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
+++ /dev/null
@@ -1,58 +0,0 @@

-title:  Recovering from ConfictingPersistentDataExceptions

-
-A 

[32/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/distributed_how_3.svg
--
diff --git a/geode-docs/images_svg/distributed_how_3.svg 
b/geode-docs/images_svg/distributed_how_3.svg
deleted file mode 100644
index a466636..000
--- a/geode-docs/images_svg/distributed_how_3.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="130 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:15Zhow_it_works-3Layer 
1Member (M1)Member 
(M2)ApplicationDistributed Region AX1Distributed Region 
AX1

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/distributed_preload.svg
--
diff --git a/geode-docs/images_svg/distributed_preload.svg 
b/geode-docs/images_svg/distributed_preload.svg
deleted file mode 100644
index 681c824..000
--- a/geode-docs/images_svg/distributed_preload.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="77 311 310 85" 
width="310pt" height="85pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 23:02ZpreloadLayer 1DistributedSystemDistributed Region(Preloaded or Normal)XYOperations for existing entry 
keys

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/distributed_replica.svg
--
diff --git a/geode-docs/images_svg/distributed_replica.svg 
b/geode-docs/images_svg/distributed_replica.svg
deleted file mode 100644
index b28d8da..000
--- a/geode-docs/images_svg/distributed_replica.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 347 310 85" 
width="310pt" height="85pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 23:02ZreplicaLayer 1DistributedSystemDistributed Region(Replica)XYAll creationsOther entry 
operations(due 
to distribution)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/distributed_replica_preload.svg
--
diff --git a/geode-docs/images_svg/distributed_replica_preload.svg 
b/geode-docs/images_svg/distributed_replica_preload.svg
deleted file mode 100644
index a40b99e..000
--- a/geode-docs/images_svg/distributed_replica_preload.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="86 275 409 265" 
width="409pt" height="265pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 23:02Zreplica_or_preloadLayer 1Member (M1) Member 
(M2)Distributed Region AXDistributed Region AXYZMember (M3)Distributed Region 
A(replica or 
preloaded)XYZDistributedSystem

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/expiration.svg
--
diff --git a/geode-docs/images_svg/expiration.svg 
b/geode-docs/images_svg/expiration.svg
deleted file mode 100644
index 8fc278b..000
--- a/geode-docs/images_svg/expiration.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="104 275 421 301" 
width="421pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:58ZexpirationLayer 1Distributed SystemConsumer Member #1Producer Member 
#1Distributed Region 
AXDistributed Region AXYYdatabaseEntry TTL1 hour: destroyConsumer Member 
#2Distributed Region AXYEntry Idle Tx="68.512695" y="9" textLength="14.501953">imefont-family="Helvetica" font-size="9" font-weight="500" fill="black" 
 >x="11.730957" y="20" textLength="82.538086">15 min: local 
 >destroyfill="url(#Obj_Gradient_11)"/>stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">Entry Idle Time15 
min: local destroy

[34/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cs_connection_pool.svg
--
diff --git a/geode-docs/images_svg/cs_connection_pool.svg 
b/geode-docs/images_svg/cs_connection_pool.svg
deleted file mode 100644
index dcba00d..000
--- a/geode-docs/images_svg/cs_connection_pool.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="103 268 246 268" 
width="246pt" height="268pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:14Zconnection_poolLayer 
1ServerClientconnection 
poolclient threads use pool connection for cache 
operationsrequests fromother clientsCache Datalistener for 
clientsclient requests,server responsesrequests toother servers

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cs_locator_discovery.svg
--
diff --git a/geode-docs/images_svg/cs_locator_discovery.svg 
b/geode-docs/images_svg/cs_locator_discovery.svg
deleted file mode 100644
index dd55275..000
--- a/geode-docs/images_svg/cs_locator_discovery.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="122 365 391 242" 
width="391pt" height="242pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:29Zp2p and cs with locatorsLayer 
1Client/Server Discovery Using LocatorsClientLocal CacheClientLocal CachePeerPeerLocatorPeerLocatorCache DataCache DataCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cs_subscriptions.svg
--
diff --git a/geode-docs/images_svg/cs_subscriptions.svg 
b/geode-docs/images_svg/cs_subscriptions.svg
deleted file mode 100644
index 9764499..000
--- a/geode-docs/images_svg/cs_subscriptions.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="229 275 261 257" 
width="261pt" height="257pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:18ZsubscriptionsLayer 
1ServerClientstroke-width=".7203"/>fill="black">fill="black" x="48.03833" y="9" textLength="63.04834">connection 
 >poolused for updates to cache andfor sending events to 
listenersevents to 
other 
clientsCache eventssubscription queuesconnections to 
clientssubscriptionconnection

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/cs_topology.svg
--
diff --git a/geode-docs/images_svg/cs_topology.svg 
b/geode-docs/images_svg/cs_topology.svg
deleted file mode 100644
index e14dd6e..000
--- a/geode-docs/images_svg/cs_topology.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="131 238 355 201" 
width="355pt" height="201pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:03ZcsLayer 1ServerServerServerApplication 
ProcessClientLocal Cacheconnection poolCache DataCache DataCache Data

[28/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/partitioned_data_buckets_1.svg
--
diff --git a/geode-docs/images_svg/partitioned_data_buckets_1.svg 
b/geode-docs/images_svg/partitioned_data_buckets_1.svg
deleted file mode 100644
index a8cf406..000
--- a/geode-docs/images_svg/partitioned_data_buckets_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 239 409 337" 
width="409pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:47Zbuckets-1Layer 1Member (M1)Partition Region 
A<
 /g>Member 
(M2)Partition Region AMember (M3)Partition Region A

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/partitioned_data_buckets_2.svg
--
diff --git a/geode-docs/images_svg/partitioned_data_buckets_2.svg 
b/geode-docs/images_svg/partitioned_data_buckets_2.svg
deleted file mode 100644
index a996ca7..000
--- a/geode-docs/images_svg/partitioned_data_buckets_2.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 239 409 337" 
width="409pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:47Zbuckets-2Layer 1Member (M1)Partition Region 
AMember (M2)Partition 
Region AMember (M3)Partition Region 
A

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/region_entry_versions_1.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_1.svg 
b/geode-docs/images_svg/region_entry_versions_1.svg
deleted file mode 100644
index ef3f074..000
--- a/geode-docs/images_svg/region_entry_versions_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="50 182 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-03 18:54Ztemp_content
 Layer 1GemFire Member CReplicated 
Region<
 /g>GemFire Member AGemFire Member BApplicationReplicated RegionX (A3)Replicated RegionApplicationApplicationX (C2)X (C3)XX

[16/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/security/implementing_security.html.md.erb
--
diff --git a/geode-docs/managing/security/implementing_security.html.md.erb 
b/geode-docs/managing/security/implementing_security.html.md.erb
deleted file mode 100644
index a38dd03..000
--- a/geode-docs/managing/security/implementing_security.html.md.erb
+++ /dev/null
@@ -1,63 +0,0 @@

-title:  Security Implementation Introduction and Overview

-
-## Security Features
-
-Encryption, SSL secure communication, authentication, and authorization 
-features help to secure the distributed system.
-
-Security features include:
-
--   **A single security interface for all components**. The single
-authentication and authorization mechanism simplifies the security
-implementation.
-It views and interacts with all components in a consistent manner. 
--   **System-wide role-based access control**.
-Roles regiment authorized operations requested by the various components.
--   **SSL communication**. Allows configuration of connections to be 
-SSL-based, rather than plain socket connections.
-You can enable SSL separately for peer-to-peer, client, JMX, gateway senders 
and receivers, and HTTP connections.
--   **Post processing of region data**. Return values for operations that
-return region values may be altered, permitting the filtering of returned data.
-
-## Overview
-
-An authentication and authorization mechanism forms the core of
-the internal security of the distributed system.
-Communications may be further protected by enabling SSL for
-data in transit.
-
-Authentication verifies the identity of communicating components,
-leading to control over participation.
-The variety of participants include peer members, servers,
-clients, originators of JMX operations, Pulse,
-gateway senders and receivers representing WAN members of the system,
-and commands arriving from `gfsh` on behalf of system users
-or administrators.
-
-Connection requests trigger the invocation of an authentication
-callback.
-This special-purpose callback is written as part of the application,
-and it attempts to authenticate the requester by whatever
-algorithm it chooses. 
-The result is either a returned principal representing the requester's
-authenticated identity or an exception indicating that the requester
-has not been authenticated.
-The principal becomes part of any request for operations,
-which go through the authorization process.
-
-
-Given authentication,
-isolation and access to cache data and system state can be further
-protected by implementing the authorization mechanism,
-also implemented as a special-purpose callback as part of the application.
-For example, the protection may be to permit only certain system administrators
-to start and stop servers. 
-The authority to do this needs to be limited to specific
-verified accounts, preventing those without the authorization. 
-An implementation of the authorization callback will require
-that an authenticate identity accompanies all requests to the system,
-and that the system maintains a representation of which identities
-are permitted to complete which actions or cache commands.
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/security/implementing_ssl.html.md.erb
--
diff --git a/geode-docs/managing/security/implementing_ssl.html.md.erb 
b/geode-docs/managing/security/implementing_ssl.html.md.erb
deleted file mode 100644
index 73bbf49..000
--- a/geode-docs/managing/security/implementing_ssl.html.md.erb
+++ /dev/null
@@ -1,209 +0,0 @@

-title:  Configuring SSL

-
-You can configure SSL for authentication between members and to protect your 
data during
-distribution. You can use SSL alone or in conjunction with the other Geode 
security options.
-Geode SSL connections use the Java Secure Sockets Extension (JSSE) package.
-
-## SSL-Configurable Components
-
-You can specify that SSL be used system-wide, or you can independently 
configure SSL for specific
-system components.  The following list shows the system components that can be 
separately configured
-to communicate using SSL, and the kind of communications to which each 
component name refers:
-
-**cluster**
-Peer-to-peer communications among members of a distributed system
-
-**gateway**
-Communication across WAN gateways from one site to another
-
-**web**
-All web-based services hosted on the configured server, which can include 
the Developer REST API
-service, the Management REST API service (used for remote cluster management) 
and the Pulse
-monitoring tool's web-based user interface.
-
-**jmx**
-Java management extension communications, including communications with 
the `gfsh` utility. 
-The Pulse monitoring tool uses JMX for server-side communication with a 
locator, but 

[08/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
--
diff --git a/geode-docs/reference/topics/gfe_cache_xml.html.md.erb 
b/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
deleted file mode 100644
index fbe289d..000
--- a/geode-docs/reference/topics/gfe_cache_xml.html.md.erb
+++ /dev/null
@@ -1,3394 +0,0 @@
-
-
-# cache Element Reference
-
-This section documents the `cache.xml` sub-elements used for Geode server 
configuration. All elements are sub-elements of the `` element.
-
-For Geode client configuration, see [client-cache Element 
Reference](client-cache.html#cc-client-cache).
-
-**API**:`org.apache.geode.cache.CacheFactory`
-
-
-
-
-Table 1. cache Element 
Attributes
-
-
-
-
-
-
-
-Attribute
-Description
-Default
-
-
-
-
-copy-on-read
-Boolean indicating whether entry value retrieval methods return direct 
references to the entry value objects in the cache (false) or copies of the 
objects (true).
-False
-
-
-is-server
-Boolean indicating whether this member is a cache server.
-False
-
-
-lock-timeout
-The timeout, in seconds, for implicit object lock requests. This 
setting affects automatic locking only, and does not apply to manual locking. 
If a lock request does not return before the specified timeout period, it is 
cancelled and returns with a failure.
-60
-
-
-lock-lease
-The timeout, in seconds, for implicit and explicit object lock leases. 
This affects both automatic locking and manual locking. Once a lock is 
obtained, it can remain in force for the lock lease time period before being 
automatically cleared by the system.
-120
-
-
-message-sync-interval
-Used for client subscription queue synchronization when this member 
acts as a server to clients and server redundancy is used. Sets the frequency 
(in seconds) at which the primary server sends messages to its secondary 
servers to remove queued events that have already been processed by the 
clients.
-1
-
-
-search-timeout
-How many seconds a netSearch operation 
can wait for data before timing out. You may want to change this based on your 
knowledge of the network load or other factors.
-300
-
-
-
-
-: Table 1. cache Element Attributes
-
-**Example:**
-
-``` pre
-
-  
-  
-
-
-  
-
-  cacheRunner.StringLoader
-
-  
-  cacheRunner.LoggingCacheListener
-
-  
-
-  
-
-```
-
-## cache-transaction-manager
-
-Specifies a transaction listener.
-
-**API:** `CacheTransactionManager`
-
-**Example:**
-
-``` pre
-
-   
- 
-   com.company.data.MyTransactionListener
-   
- jdbc:cloudscape:rmi:MyData
-   
- 
- ...  
- 
-   com.company.data.MyTransactionWriter
-   
- jdbc:cloudscape:rmi:MyData
-   
-   
- 
-.. .
-
-```
-
-## transaction-listener
-
-When a transaction ends, its thread calls the TransactionListener to perform 
the appropriate follow-up for successful commits, failed commits, or voluntary 
rollbacks.
-
-Specify the Java class and its initialization parameters with the 
`` and `` sub-elements. See [class-name and 
parameter](cache_xml.html#class-name_parameter).
-
-## transaction-writer
-
-When you commit a transaction, a TransactionWriter can perform additional 
tasks, including aborting the transaction.
-
-Specify the Java class and its initialization parameters with the 
`` and `` sub-elements. See [class-name and 
parameter](cache_xml.html#class-name_parameter).
-
-## dynamic-region-factory
-
-The `` element configures a dynamic region factory for 
this cache. You can use this element to dynamically create regions in your 
application code. Use the createDynamicRegion() method of the org.apache.geode.cache.DynamicRegionFactory class in your Java 
code to dynamically create regions.
-
-**Note:**
-You can not use this element to dynamically create *partitioned* regions.
-
-We recommend that you use functions to dynamically create regions. See 
[Creating Regions 
Dynamically](../../developing/region_options/dynamic_region_creation.html).
-
-The optional `` sub-element specifies the directory to store the 
persistent files that are used for dynamic region bookkeeping. It defaults to 
the current directory.
-
-Set the `pool-name` attribute to set the name of the connection pool used by 
client applications in a client/server cache configuration. Do not specify the 
`pool-name` attribute in servers or peers.
-
-**API:** `org.apache.geode.cache.DynamicRegionFactory`
-
-
-
-| Attribute | Description  
  | 
Default |
-|---||-|
-| disable-persist-backup| When set to false, 

[38/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/getting_started/querying_quick_reference.html.md.erb
--
diff --git a/geode-docs/getting_started/querying_quick_reference.html.md.erb 
b/geode-docs/getting_started/querying_quick_reference.html.md.erb
deleted file mode 100644
index 9a06d1f..000
--- a/geode-docs/getting_started/querying_quick_reference.html.md.erb
+++ /dev/null
@@ -1,694 +0,0 @@

-title:  Geode Querying FAQ and Examples

-
-This topic answers some frequently asked questions on querying functionality. 
It provides examples to help you get started with Geode querying.
-
-
-For additional information on Geode querying, see 
[Querying](../developing/querying_basics/chapter_overview.html).
-
--   [How do I write and execute a query against a Geode 
region?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_7A4D2C6A4E2C4F4384C158FFCA9CA1C0)
--   [Can I see query string examples, listed by query 
type?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_641D97CD874D4182961C85429ACA1B05)
--   [Which APIs should I use to write my 
queries?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5383407F9D004D4EB4E695252EBA1EF0)
--   [How do I invoke an object's method in a 
query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_3E6E4B33D57846008EF4404D2B687597)
--   [Can I invoke a static method on an object in a 
query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_9221C29BC1FD49D7BBD26BB34D5BDEB8)
--   [How do I write a reusable 
query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_907DBBBA1AEC4570A15B3491B0A7DF0E)
--   [When should I create indexes to use in my 
queries?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_3A9528E8E43140BAA0D5A1457CCAB2D2)
--   [How do I create an 
index?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_76CDCCFBDB134A339DBE556C28D48F11)
--   [Can I query a partitioned region? Can I perform a join query on a 
partitioned 
region?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_EDD17817450C4FC0B510CD87DB2FCD16)
--   [How can I improve the performance of a partitioned region 
query?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_5FF905E0D10D4CDF9E6F49A70848AF69)
--   [Which query language elements are supported in 
Geode?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_FBC59A5420FD40D6907A302A1D50DF7E)
--   [How do I debug 
queries?](querying_quick_reference.html#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_314B88A55B514B88A12DC36227A2D4EF)
--   [Can I use implicit attributes or methods in my 
query?](#reference_D5CE64F5FD6F4A808AEFB748C867189E__implicit_attributes)
--   [How do I perform a case-insensitive search on a field in 
OQL?](#reference_D5CE64F5FD6F4A808AEFB748C867189E__section_ayq_hqw_1r)
-
-## How do I write and execute a query against a Geode 
region?
-
-To write and execute a query in Geode, you can use any of the following 
mechanisms. Sample query code follows.
-
--   Geode querying APIs
--   [gfsh](../tools_modules/gfsh/chapter_overview.html) command-line 
interface; in particular the 
[query](../tools_modules/gfsh/command-pages/query.html) command
--   REST API [query 
endpoints](../rest_apps/rest_queries.html#concept_mmg_d35_m4)
-
-**Sample Geode Query Code (Java)**
-
-``` pre
-// Identify your query string.
- String queryString = "SELECT * FROM /exampleRegion";
- 
- // Get QueryService from Cache.
- QueryService queryService = cache.getQueryService();
- 
- // Create the Query Object.
- Query query = queryService.newQuery(queryString);
- 
- // Execute Query locally. Returns results set.
- SelectResults results = (SelectResults)query.execute();
- 
- // Find the Size of the ResultSet.
- int size = results.size();
- 
- // Iterate through your ResultSet.
- Portfolio p = (Portfolio)results.iterator().next(); /* Region containing 
Portfolio object. */
-```
-
-## Can I see query string examples, listed by query 
type?
-
-The following example query strings use the `/exampleRegion` whose keys are 
the portfolio ID and whose values correspond to the summarized data shown in 
the following class definitions:
-
-``` pre
-class Portfolio implements DataSerializable {
-   int ID;
-   String type;
-   String status;
-   Map positions;
-}
-class Position implements DataSerializable {
-   String secId;
-   double mktValue;
-   double qty;
-}
-```
-
-**Basic WHERE Clause Examples**
-
-In the following examples, the status field is type String and the ID field is 
type int. See [Supported 
Literals](../developing/query_additional/literals.html#literals) for a complete 
list of literals 

[42/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/query_additional/supported_keywords.html.md.erb
--
diff --git 
a/geode-docs/developing/query_additional/supported_keywords.html.md.erb 
b/geode-docs/developing/query_additional/supported_keywords.html.md.erb
deleted file mode 100644
index 1a257f6..000
--- a/geode-docs/developing/query_additional/supported_keywords.html.md.erb
+++ /dev/null
@@ -1,31 +0,0 @@

-title:  Supported Keywords

-
-| Query Language Keyword | Description 



| Example   


 |
-||-||
-| AND| Logical operator used to create complex expressions 
by combining two or more expressions to produce a Boolean result. When you 
combine two conditional expressions using the AND operator, both conditions 
must evaluate to true for the entire expression to be true. 
 | See 
[Operators](operators.html#operators)   

   |
-| AS | Used to provide a label for a path expression so 
you can refer to the path by the label later.   


   | See [Aliases and 
Synonyms](../query_select/the_from_clause.html#the_from_clause__section_AB1734C16DC348479C00FD6829B933AA)

 |
-| COUNT  | Returns the number of results that match the 
provided criteria.  


   | See 
[COUNT](../query_select/the_select_statement.html#concept_85AE7D6B1E2941ED8BD2A8310A81753E__section_B2CBA00EB83F463DAF4769D7859C64C8)

  |
-| DISTINCT   | Restricts the select statement to unique results 
(eliminates duplicates).


   | See 
[DISTINCT](../query_select/the_select_statement.html#concept_85AE7D6B1E2941ED8BD2A8310A81753E__section_972EE73A6F3E4427B6A99DB4EDF5860D)

   |
-| ELEMENT| Query function. Extracts a single element from a 
collection or array. This function throws a `FunctionDomainException ` if the 
argument is not a collection or array with exactly one element. 

 | See [Preset Query 
Functions](../query_select/the_select_statement.html#concept_85AE7D6B1E2941ED8BD2A8310A81753E__section_69DCAD624E9640028BC86FD67649DEB2)
 |
-| FROM   | You can access any object or object attribute that 
is available in the current scope of the query.

[41/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/query_select/the_where_clause.html.md.erb
--
diff --git a/geode-docs/developing/query_select/the_where_clause.html.md.erb 
b/geode-docs/developing/query_select/the_where_clause.html.md.erb
deleted file mode 100644
index fd2405e..000
--- a/geode-docs/developing/query_select/the_where_clause.html.md.erb
+++ /dev/null
@@ -1,336 +0,0 @@

-title:  WHERE Clause

-
-
-Each FROM clause expression must resolve to a collection of objects. The 
collection is then available for iteration in the query expressions that follow 
in the WHERE clause.
-
-For example:
-
-``` pre
-SELECT DISTINCT * FROM /exampleRegion p WHERE p.status = 'active'
-```
-
-The entry value collection is iterated by the WHERE clause, comparing the 
status field to the string 'active'. When a match is found, the value object of 
the entry is added to the return set.
-
-In the next example query, the collection specified in the first FROM clause 
expression is used by the rest of the SELECT statement, including the second 
FROM clause expression.
-
-``` pre
-SELECT DISTINCT * FROM /exampleRegion, positions.values p WHERE p.qty > 1000.00
-```
-
-## Implementing equals and hashCode Methods
-
-You must implement the `equals` and `hashCode` methods in your custom objects 
if you are doing ORDER BY and DISTINCT queries on the objects. The methods must 
conform to the properties and behavior documented in the online Java API 
documentation for `java.lang.Object`. Inconsistent query results may occur if 
these methods are absent.
-
-If you have implemented `equals` and `hashCode` methods in your custom 
objects, you must provide detailed implementations of these methods so that 
queries execute properly against the objects. For example, assume that you have 
defined a custom object (CustomObject) with the following variables:
-
-``` pre
-int ID
-int otherValue
-```
-
-Let's put two CustomObjects (we'll call them CustomObjectA and CustomObjectB) 
into the cache:
-
-CustomObjectA:
-
-``` pre
-ID=1
-otherValue=1
-```
-
-CustomObjectB:
-
-``` pre
-ID=1
-otherValue=2
-```
-
-If you have implemented the equals method to simply match on the ID field (ID 
== ID), queries will produce unpredictable results.
-
-The following query:
-
-``` pre
-SELECT * FROM /CustomObjects c 
-WHERE c.ID > 1 AND c.ID < 3 
-AND c.otherValue > 0 AND c.otherValue < 3
-```
-
-returns two objects, however the objects will be two of either CustomObjectA 
or CustomObjectB.
-
-Alternately, the following query:
-
-``` pre
-SELECT * FROM /CustomObjects c 
-WHERE c.ID > 1 AND c.ID < 3 
-AND c.otherValue > 1 AND c.otherValue < 3
-```
-
-returns either 0 results or 2 results of CustomObjectB, depending on which 
entry is evaluated last.
-
-To avoid unpredictable querying behavior, implement detailed versions of the 
`equals` and `hashCode` methods.
-
-If you are comparing a non-primitive field of the object in the WHERE clause, 
use the `equals` method instead of the `=` operator. For example instead of 
`nonPrimitiveObj = objToBeCompared` use 
`nonPrimitiveObj.equals(objToBeCompared)`.
-
-## Querying Serialized Objects
-
-Objects must implement serializable if you will be querying partitioned 
regions or if you are performing client-server querying.
-
-If you are using PDX serialization, you can access the values of individual 
fields without having to deserialize the entire object. This is accomplished by 
using PdxInstance, which is a wrapper around the serialized stream. The 
PdxInstance provides a helper method that takes field-name and returns the 
value without deserializing the object. While evaluating the query, the query 
engine will access field values by calling the getField method thus avoiding 
deserialization.
-
-To use PdxInstances in querying, ensure that PDX serialization reads are 
enabled in your server's cache. In gfsh, execute the following command before 
starting up your data members:
-
-``` pre
-gfsh>configure pdx --read-serialized=true
-```
-
-See [configure 
pdx](../../tools_modules/gfsh/command-pages/configure.html#topic_jdkdiqbgphqh) 
for more information.
-
-In cache.xml, set the following:
-
-``` pre
-// Cache configuration setting PDX read behavior 
-
-  
-  ...
-  
-
-```
-
-## Attribute Visibility
-
-You can access any object or object attribute that is available in the current 
scope of a query. In querying, an object's attribute is any identifier that can 
be mapped to a public field or method in the object. In the FROM specification, 
any object that is in scope is valid. Therefore, at the beginning of a query, 
all locally cached regions and their attributes are in scope.
-
-For attribute Position.secId which is public and has getter method 
"getSecId()", the query can be written as the following:
-
-``` pre
-SELECT DISTINCT * FROM /exampleRegion p WHERE p.position1.secId = '1'
-SELECT 

[30/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/how_partitioning_works_2.svg
--
diff --git a/geode-docs/images_svg/how_partitioning_works_2.svg 
b/geode-docs/images_svg/how_partitioning_works_2.svg
deleted file mode 100644
index 6351a28..000
--- a/geode-docs/images_svg/how_partitioning_works_2.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="68 212 385 412" 
width="385pt" height="412pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:43Zhow_it_works_2Layer 
1Partitioned Region ALogical ViewXYZPartitioned Region APh
 ysical ViewNo local 
dataMachine 1Partitioned Region 
AXMachine 
2Partitioned Region AYMachine 3Z

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/http_module_cs_with_locator.svg
--
diff --git a/geode-docs/images_svg/http_module_cs_with_locator.svg 
b/geode-docs/images_svg/http_module_cs_with_locator.svg
deleted file mode 100644
index 3b8e6a3..000
--- a/geode-docs/images_svg/http_module_cs_with_locator.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="77 333 373 279" 
width="373pt" height="279pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:40Zcs with 
locatorLayer 1Partitioned <
 /tspan>Session 
DataPartitioned Session DataServerServerPartitioned Session Data
 Application Server 
InstanceClientapp server requestsLocal Cacheconnection 
poolLocatorprovides discovery and load balancing 
servicesPartitioned 
Session 
Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/http_module_p2p_with_locator.svg
--
diff --git a/geode-docs/images_svg/http_module_p2p_with_locator.svg 
b/geode-docs/images_svg/http_module_p2p_with_locator.svg
deleted file mode 100644
index 3c7c0b4..000
--- a/geode-docs/images_svg/http_module_p2p_with_locator.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="59 348 499 191" 
width="499pt" height="191pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:39Zp2p with 
locatorLayer 1Application Server InstanceCacheApplication Server InstanceCacheApplication Server InstanceCacheapp server 
requestsapp server 
requestsapp server 
requestsReplicated 
Session 
DataReplicated Session DataReplicated Session DataLocatorprovides discovery and load 
balancing services

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/locator_discovery.svg
--
diff --git a/geode-docs/images_svg/locator_discovery.svg 
b/geode-docs/images_svg/locator_discovery.svg
deleted file mode 100644
index 53e9f3b..000
--- a/geode-docs/images_svg/locator_discovery.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="81 317 450 160" 
width="450pt" height="160pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:26ZlocatorsLayer 1PeerPeerPeer Discovery Using 
Locators LocatorPeerLocatorCache DataCache DataCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/member_severe_alert.svg
--
diff --git a/geode-docs/images_svg/member_severe_alert.svg 
b/geode-docs/images_svg/member_severe_alert.svg
deleted file mode 100644
index 8614503..000
--- a/geode-docs/images_svg/member_severe_alert.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="94 248 368 267" 
width="368pt" height="267pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:59Zmember severe 
alertLayer 11. CACHE_OPERATIONCache ServerReplicated RegionCache 
ServerReplicated 
RegionLocatorClientx="12.466797" y="10" textLength="25.566406">Clientx1="346.5" y1="461.25" x2="346.5" y2="421.948" 
 >marker-end="url(#FilledArrow_Marker)" stroke="#252525" stroke-linecap="round" 
 >stroke-linejoin="round" stroke-width=".7203"/>d="M 323.91 461.25 L 369.09 461.25 C 372.76822 461.25 375.75 464.23178 375.75 
 >467.91 L 375.75 490.59 C 375.75 494.26822 372.76822 497.25 

[20/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/heap_use/off_heap_management.html.md.erb
--
diff --git a/geode-docs/managing/heap_use/off_heap_management.html.md.erb 
b/geode-docs/managing/heap_use/off_heap_management.html.md.erb
deleted file mode 100644
index 0c8bf7c..000
--- a/geode-docs/managing/heap_use/off_heap_management.html.md.erb
+++ /dev/null
@@ -1,192 +0,0 @@

-title: Managing Off-Heap Memory

-
-
-
-Geode can be configured to store region values in off-heap memory, which is 
memory within the JVM that is not subject to Java garbage collection.
-
-Garbage collection (GC) within a JVM can prove to be a performance impediment. 
A server cannot exert control over when garbage collection within the JVM heap 
memory takes place, and the server has little control over the triggers for 
invocation. Off-heap memory offloads values to a storage area that is not 
subject to Java GC. By taking advantage of off-heap storage, an application can 
reduce the amount of heap storage that is subject to GC overhead.
-
-Off-heap memory works in conjunction with the heap, it does not replace it. 
The keys are stored in heap memory space. Geode's own memory manager handles 
the off-heap memory with better performance than the Java garbage collector 
would for certain sets of region data.
-
-The resource manager monitors the contents of off-heap memory and invokes 
memory management operations in accordance with two thresholds similar to those 
used for monitoring the JVM heap: `eviction-off-heap-percentage` and 
`critical-off-heap-percentage`.
-
-## On-heap and Off-heap Objects
-
-The following objects are always stored in the JVM heap:
-
--   Region metadata
--   Entry metadata
--   Keys
--   Indexes
--   Subscription queue elements
-
-The following objects can be stored in off-heap memory:
-
--   Values - maximum value size is 2GB
--   Reference counts
--   List of free memory blocks
--   WAN queue elements
-
-**Note:**
-Do not use functional range indexes with off-heap data, as they are not 
supported. An attempt to do so generates an exception.
-
-## Off-heap Recommendations
-
-Off-heap storage is best suited to data patterns where:
-
--   Stored values are relatively uniform in size
--   Stored values are mostly less than 128K in size
--   The usage patterns involve cycles of many creates followed by destroys or 
clear
--   The values do not need to be frequently deserialized
--   Many of the values are long-lived reference data
-
-Be aware that Geode has to perform extra work to access the data stored in 
off-heap memory since it is stored in serialized form. This extra work may 
cause some use cases to run slower in an off-heap configuration, even though 
they use less memory and avoid garbage collection overhead. However, even with 
the extra deserialization, off-heap storage may give you the best performance. 
Features that may increase overhead include
-
--   frequent updates
--   stored values of widely varying sizes
--   deltas
--   queries
-
-## Implementation Details
-
-The off-heap memory manager is efficient at handling region data values that 
are all the same size or are of fixed sizes. With fixed and same-sized data 
values allocated within the off-heap memory, freed chunks can often be re-used, 
and there is little or no need to devote cycles to defragmentation.
-
-Region values that are less than or equal to eight bytes in size will not 
reside in off-heap memory, even if the region is configured to use off-heap 
memory. These very small size region values reside in the JVM heap in place of 
a reference to an off-heap location. This performance enhancement saves space 
and load time.
-
-## Controlling Off-heap Use with the Resource Manager
-
-The Geode resource manager controls off-heap memory by means of two 
thresholds, in much the same way as it does JVM heap memory. See [Using the 
Geode Resource Manager](heap_management.html#how_the_resource_manager_works). 
The resource manager prevents the cache from consuming too much off-heap memory 
by evicting old data. If the off-heap memory manager is unable to keep up, the 
resource manager refuses additions to the cache until the off-heap memory 
manager has freed an adequate amount of memory.
-
-The resource manager has two threshold settings, each expressed as a 
percentage of the total off-heap memory. Both are disabled by default.
-
-1.  **Eviction Threshold**. The percentage of off-heap memory at which 
eviction should begin. Evictions continue until the resource manager determines 
that off-heap memory use is again below the eviction threshold. Set the 
eviction threshold with the `eviction-off-heap-percentage` region attribute. 
The resource manager enforces an eviction threshold only on regions with the 
HEAP\_LRU characteristic. If critical threshold is non-zero, the default 
eviction threshold is 5% below the critical 

[39/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/transactions/transaction_jta_gemfire_example.html.md.erb
--
diff --git 
a/geode-docs/developing/transactions/transaction_jta_gemfire_example.html.md.erb
 
b/geode-docs/developing/transactions/transaction_jta_gemfire_example.html.md.erb
deleted file mode 100644
index 6795158..000
--- 
a/geode-docs/developing/transactions/transaction_jta_gemfire_example.html.md.erb
+++ /dev/null
@@ -1,31 +0,0 @@

-title:  Geode JTA Transaction Example

-
-An example code fragment shows how to run a JTA global transaction using Geode 
as the JTA transaction manager.
-
-The external data sources used in this transaction are configured in the 
`cache.xml` file. See [Configuring Database Connections Using 
JNDI](configuring_db_connections_using_JNDI.html#topic_A5E3A67C808D48C08E1F0DC167C5C494)
 for a configuration example.
-
-``` pre
-Region r = ...; // the  region data source 
-ds = ...; // other data source
-
-  try  { 
- Context ctx = cache.getJNDIContext();  
- Connection conn =  null;
- UserTransaction tx = (UserTransaction) 
ctx.lookup("java:/UserTransaction"); 
- tx.begin();
- conn = ds.getConnection();
- Statement stmt = conn.createStatement();
- String sqlSTR =  "insert into " + tableName + " values ( )";
- stmt.executeUpdate(sqlSTR);   
- r.put("key", "value");
- stmt.close(); 
- tx.commit();
- conn.close();
-   } catch (NamingException e) { 
- // handle the exception   
-   }
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/transactions/transaction_semantics.html.md.erb
--
diff --git 
a/geode-docs/developing/transactions/transaction_semantics.html.md.erb 
b/geode-docs/developing/transactions/transaction_semantics.html.md.erb
deleted file mode 100644
index 58b3e47..000
--- a/geode-docs/developing/transactions/transaction_semantics.html.md.erb
+++ /dev/null
@@ -1,37 +0,0 @@

-title:  Geode Cache Transaction Semantics

-
-Geode transaction semantics differ in some ways from the 
Atomicity-Consistency-Isolation-Durability (ACID) semantics of traditional 
relational databases. For performance reasons, Geode transactions do not adhere 
to ACID constraints by default, but can be configured for ACID support as 
described in this section.
-
-## Atomicity
-
-Atomicity is “all or nothing” behavior: a transaction completes 
successfully only when all of the operations it contains complete successfully. 
If problems occur during a transaction, perhaps due to other transactions with 
overlapping changes, the transaction cannot successfully complete until the 
problems are resolved.
-
-Geode transactions provide atomicity and realize speed by using a reservation 
system, instead of using the traditional relational database technique of a 
two-phase locking of rows. The reservation prevents other, intersecting 
transactions from completing, allowing the commit to check for conflicts and to 
reserve resources in an all-or-nothing fashion prior to making changes to the 
data. After all changes have been made, locally and remotely, the reservation 
is released. With the reservation system, an intersecting transaction is simply 
discarded. The serialization of obtaining locks is avoided. See [Committing 
Transactions](how_cache_transactions_work.html#concept_sbj_lj1_wk) for details 
on the two-phase commit protocol that implements the reservation system.
-
-## Consistency
-
-Consistency requires that data written within a transaction must observe the 
key and value constraints established for the affected region. Note that 
validity of the transaction is the responsibility of the application.
-
-## Isolation
-
-Isolation assures that operations will see either the pre-transaction state of 
the system or its post-transaction state, but not the transitional state that 
occurs while a transaction is in progress. Write operations in a transaction 
are always confirmed to ensure that stale values are not written. As a 
distributed cache-based system optimized for performance, Geode in its default 
configuration does not enforce read isolation. Geode transactions support 
repeatable read isolation, so once the committed value is read for a given key, 
it always returns that same value. If a transaction write, such as put or 
invalidate, deletes a value for a key that has already been read, subsequent 
reads return the transactional reference.
-
-In the default configuration, Geode isolates transactions at the process 
thread level, so while a transaction is in progress, its changes are visible 
only inside the thread that is running the transaction. Threads inside the same 
process and in other processes cannot 

[23/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/transactions_replicate_local_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_local_1.svg 
b/geode-docs/images_svg/transactions_replicate_local_1.svg
deleted file mode 100644
index 47bb4e7..000
--- a/geode-docs/images_svg/transactions_replicate_local_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="41 158 319 301" 
width="319pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:04Zreplicate-localLayer 
1MemberCacheReplicate Region AJava ApplicationXT1YZRegion AX1Y1Region AY2Z2T2Transaction T1Transaction T2

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_no_ack_1.svg 
b/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
deleted file mode 100644
index 1d94d72..000
--- a/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="133 203 584 337" 
width="584pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:00Zreplicate-no-ack-1Layer 
1W1X1X2Member (M1)CacheReplicate Region AJava ApplicationWMember 
(M2)Replicate Region 
BXRegion AW1Region 
BX1Transaction T1CacheReplicate Region 
AWMember (M3)CacheReplicate Region 
BX2Replicate Region 
BXTransaction T2Java Application

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_no_ack_2.svg 
b/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
deleted file mode 100644
index 8b4d41a..000
--- a/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="19 148 584 337" 
width="584pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:02Zreplicate-no-ack-2Layer 
1Member (M1)CacheReplicate Region AJava ApplicationW1Member (M2)Replicate Region 
B
 X2CacheReplicate Region AW1Member 
(M3)CacheReplicate Region 
BX1Java Application

[27/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/region_entry_versions_2.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_2.svg 
b/geode-docs/images_svg/region_entry_versions_2.svg
deleted file mode 100644
index 0efcc23..000
--- a/geode-docs/images_svg/region_entry_versions_2.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="17 33 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-03 01:12ZCanvas 9Layer 1Member C
 Replicated 
RegionMember 
AMember 
BApplicationReplicated 
RegionX 
(A3)Replicated RegionApplicationApplicationX 
(A3)X 
(C3)X (A3)X 
(A3)(ignored)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/region_entry_versions_3.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_3.svg 
b/geode-docs/images_svg/region_entry_versions_3.svg
deleted file mode 100644
index 105db57..000
--- a/geode-docs/images_svg/region_entry_versions_3.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="26 101 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-03 01:12ZCanvas 8Layer 1Member CReplicated RegionMember A 
Member BApplicationReplicated RegionX (C3)Replicated 
RegionApplicationApplicationX (C3)X (C3)X 
(C3)X 
(C3)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/server_client_event_dist.svg
--
diff --git a/geode-docs/images_svg/server_client_event_dist.svg 
b/geode-docs/images_svg/server_client_event_dist.svg
deleted file mode 100644
index 2d726cd..000
--- a/geode-docs/images_svg/server_client_event_dist.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="27 275 293 301" 
width="293pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:51Z
 cs-event-distributionLayer 
1Client 
1Region Apool-name = ServerPoolinterest in XreceiveValues = trueServerRegion AXCache 
ServerClient 2XUpdate/CreateRegion Apool-name = ServerPoolinterest in XreceiveValues = 
falsepool 
“ServerPool”(with 
subscriptions enabled)pool 
“ServerPool”(with 
subscriptions enabled)Update/CreateInvalidateXX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/server_discovery.svg
--
diff --git a/geode-docs/images_svg/server_discovery.svg 
b/geode-docs/images_svg/server_discovery.svg
deleted file mode 100644
index 661b66f..000
--- a/geode-docs/images_svg/server_discovery.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="176 248 373 341" 
width="373pt" height="341pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:31Zhow_server_discovery_worksLayer 
1Server #1ClientLocal Cacheconnection poolLocatorsend address and load inforequest serverconnectionServer 
#2Cache DataCache Datalistening on 10.80.100.1 :  
40404listening on 10.80.100.2 :  40404listening on lucy : 4locator atlucy : 41use 
10.80.100.2 : 404042client/server communication3

[18/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
--
diff --git 
a/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
 
b/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
deleted file mode 100644
index b8445f2..000
--- 
a/geode-docs/managing/monitor_tune/multicast_communication_runtime_considerations.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@

-title:  Run-time Considerations for Multicast

-
-When you use multicast for messaging and data distribution, you need to 
understand how the health monitoring setting works and how to control memory 
use.
-
-**Multicast Health Monitor**
-
-The Geode management and monitoring system is supplemented by a 
maxRetransmissionRatio health monitoring setting for distributed system 
members. This ratio is the number of retransmission requests received divided 
by the number of multicast datagrams written. If the ratio is at 1.0, the 
member is retransmitting as many packets as it originally sent. Retransmissions 
are point-to-point, and many processes may request retransmission, so this 
number can get quite high if problems occur. The default value for 
maxRetransmissionRatio is 0.2.
-
-For example, consider a distributed system with one producer and two consumers 
of cache events using multicast to transmit cache updates. The new member is 
added, which is running on a machine without multicast enabled. As a result, 
there is a retransmission request for every cache update, and the 
maxRetransmissionRatio changes to 1.0.
-
-**Controlling Memory Use on Geode Hosts with Multicast**
-
-Running out of memory can impede a member’s performance and eventually lead 
to severe errors.
-
-When data is distributed over multicast, Geode incurs a fixed overhead of 
memory reserved for transmission buffers. A specified amount of memory is 
reserved for each distributed region. These producer-side buffers are used only 
when a receiver is not getting enough CPU to read from its own receiving buffer 
as quickly as the producer is sending. In this case, the receiver complains of 
lost data. The producer then retrieves the data, if it still exists in its 
buffer, and resends to the receiver.
-
-Tuning the transmission buffers requires a careful balance. Larger buffers 
mean that more data remains available for retransmission, providing more 
protection in case of a problem. On the other hand, a larger amount of reserved 
memory means that less memory is available for caching.
-
-You can adjust the transmission buffer size by resetting the 
mcast-send-buffer-size parameter in the `gemfire.properties` file:
-
-``` pre
-mcast-send-buffer-size=45000
-```
-
-**Note:**
-The maximum buffer size is constrained only by the limits of your system. If 
you are not seeing problems that could be related to lack of memory then do not 
change the default, since it provides greater protection in case of network 
problems.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
--
diff --git 
a/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
 
b/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
deleted file mode 100644
index d339a55..000
--- 
a/geode-docs/managing/monitor_tune/multicast_communication_testing_multicast_speed_limits.html.md.erb
+++ /dev/null
@@ -1,128 +0,0 @@

-title:  Testing Multicast Speed Limits

-
-TCP automatically adjusts its speed to the capability of the processes using 
it and enforces bandwidth sharing so that every process gets a turn. With 
multicast, you must determine and explicitly set those limits.
-
-
-Without the proper configuration, multicast delivers its traffic as fast as 
possible, overrunning the ability of consumers to process the data and locking 
out other processes that are waiting for the bandwidth. You can tune your 
multicast and unicast behavior using mcast-flow-control in `gemfire.properties`.
-
-**Using Iperf**
-
-Iperf is an open-source TCP/UDP performance tool that you can use to find your 
site’s maximum rate for data distribution over multicast. Iperf can be 
downloaded from web sites such as the National Laboratory for Applied Network 
Research (NLANR).
-
-Iperf measures maximum bandwidth, allowing you to tune parameters and UDP 
characteristics. Iperf reports statistics on bandwidth, delay jitter, and 
datagram loss. On Linux, you can redirect this output to a file; on Windows, 
use the -o filename parameter.
-
-Run each test for ten minutes to make sure any potential problems have 

[17/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/monitor_tune/udp_communication.html.md.erb
--
diff --git a/geode-docs/managing/monitor_tune/udp_communication.html.md.erb 
b/geode-docs/managing/monitor_tune/udp_communication.html.md.erb
deleted file mode 100644
index 2f85709..000
--- a/geode-docs/managing/monitor_tune/udp_communication.html.md.erb
+++ /dev/null
@@ -1,33 +0,0 @@

-title:  UDP Communication

-
-You can make configuration adjustments to improve multicast and unicast UDP 
performance of peer-to-peer communication.
-
-You can tune your Geode UDP messaging to maximize throughput. There are two 
main tuning goals: to use the largest reasonable datagram packet sizes and to 
reduce retransmission rates. These actions reduce messaging overhead and 
overall traffic on your network while still getting your data where it needs to 
go. Geode also provides statistics to help you decide when to change your UDP 
messaging settings.
-
-Before you begin, you should understand Geode [Basic Configuration and 
Programming](../../basic_config/book_intro.html). See also the general 
communication tuning and multicast-specific tuning covered in [Socket 
Communication](socket_communication.html) and [Multicast 
Communication](multicast_communication.html#multicast).
-
-## UDP Datagram Size
-
-You can change the UDP datagram size with the Geode property 
udp-fragment-size. This is the maximum packet size for transmission over UDP 
unicast or multicast sockets. When possible, smaller messages are combined into 
batches up to the size of this setting.
-
-Most operating systems set a maximum transmission size of 64k for UDP 
datagrams, so this setting should be kept under 60k to allow for communication 
headers. Setting the fragment size too high can result in extra network traffic 
if your network is subject to packet loss, as more data must be resent for each 
retransmission. If many UDP retransmissions appear in DistributionStats, you 
maybe achieve better throughput by lowering the fragment size.
-
-## UDP Flow Control
-
-UDP protocols typically have a flow control protocol built into them to keep 
processes from being overrun by incoming no-ack messages. The Geode UDP flow 
control protocol is a credit based system in which the sender has a maximum 
number of bytes it can send before getting its byte credit count replenished, 
or recharged, by its receivers. While its byte credits are too low, the sender 
waits. The receivers do their best to anticipate the sender’s recharge 
requirements and provide recharges before they are needed. If the senders 
credits run too low, it explicitly requests a recharge from its receivers.
-
-This flow control protocol, which is used for all multicast and unicast no-ack 
messaging, is configured using a three-part Geode property mcast-flow-control. 
This property is composed of:
-
--   byteAllowance—Determines how many bytes (also referred to as credits) 
can be sent before receiving a recharge from the receiving processes.
--   rechargeThreshold—Sets a lower limit on the ratio of the sender’s 
remaining credit to its byteAllowance. When the ratio goes below this limit, 
the receiver automatically sends a recharge. This reduces recharge request 
messaging from the sender and helps keep the sender from blocking while waiting 
for recharges.
--   rechargeBlockMs—Tells the sender how long to wait while needing a 
recharge before explicitly requesting one.
-
-In a well-tuned system, where consumers of cache events are keeping up with 
producers, the byteAllowance can be set high to limit flow-of-control messaging 
and pauses. JVM bloat or frequent message retransmissions are an indication 
that cache events from producers are overrunning consumers.
-
-## UDP Retransmission Statistics
-
-Geode stores retransmission statistics for its senders and receivers. You can 
use these statistics to help determine whether your flow control and fragment 
size settings are appropriate for your system.
-
-The retransmission rates are stored in the DistributionStats ucastRetransmits 
and mcastRetransmits. For multicast, there is also a receiver-side statistic 
mcastRetransmitRequests that can be used to see which processes aren't keeping 
up and are requesting retransmissions. There is no comparable way to tell which 
receivers are having trouble receiving unicast UDP messages.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb
--
diff --git 
a/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb 
b/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb
deleted file mode 100644
index 62a10bf..000
--- a/geode-docs/managing/network_partitioning/chapter_overview.html.md.erb
+++ 

[40/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/developing/transactions/JTA_transactions.html.md.erb
--
diff --git a/geode-docs/developing/transactions/JTA_transactions.html.md.erb 
b/geode-docs/developing/transactions/JTA_transactions.html.md.erb
deleted file mode 100644
index 31d0cbb..000
--- a/geode-docs/developing/transactions/JTA_transactions.html.md.erb
+++ /dev/null
@@ -1,226 +0,0 @@

-title: JTA Global Transactions with Geode

-
-
-Use JTA global transactions to coordinate Geode cache transactions and JDBC 
transactions.
-
-JTA is a standard Java interface you can use to coordinate Geode cache 
transactions and JDBC transactions globally under one umbrella. JTA provides 
direct coordination between the Geode cache and another transactional resource, 
such as a database. The parties involved in a JTA transaction include:
-
--   The Java application, responsible for starting the global transaction
--   The JTA transaction manager, responsible for opening, committing, and 
rolling back transactions
--   The transaction resource managers, including the Geode cache transaction 
manager and the JDBC resource manager, responsible for managing operations in 
the cache and database respectively
-
-Using JTA, your application controls all transactions in the same standard 
way, whether the transactions act on the Geode cache, a JDBC resource, or both 
together. When a JTA global transaction is done, the Geode transaction and the 
database transaction are both complete.
-
-When using JTA global transactions with Geode, you have three options:
-
-1.  Coordinate with an external JTA transaction manager in a container (such 
as WebLogic or JBoss)
-2.  Set Geode as the “last resource” while using a container (such as 
WebLogic or JBoss) as the JTA transaction manager
-3.  Have Geode act as the JTA transaction manager
-
-An application creates a global transaction by using 
`javax.transaction.UserTransaction` bound to the JNDI context 
`java:/UserTransaction` to start and terminate transactions. During the 
transaction, cache operations are done through Geode as usual as described in 
[Geode Cache Transactions](cache_transactions.html#topic_e15_mr3_5k).
-
-**Note:**
-See the Sun documentation for more information on topics such as JTA, 
`javax.transaction`, committing and rolling back global transactions, and the 
related exceptions.
-
--   **[Coordinating with External JTA Transactions 
Managers](#concept_cp1_zx1_wk)**
-
-Geode can work with the JTA transaction managers of several containers 
like JBoss, WebLogic, GlassFish, and so on.
-
--   **[Using Geode as the "Last Resource" in a Container-Managed JTA 
Transaction](#concept_csy_vfb_wk)**
-
-The "last resource" feature in certain 3rd party containers such as 
WebLogic allow the use one non-XAResource (such as Geode) in a transaction with 
multiple XAResources while ensuring consistency.
-
--   **[Using Geode as the JTA Transaction Manager](#concept_8567sdkbigige)**
-
-You can also use Geode as the JTA transaction manager.
-
--   **[Behavior of Geode Cache Writers and Loaders Under 
JTA](cache_plugins_with_jta.html)**
-
-When Geode participates in a global transactions, you can still have Geode 
cache writers and cache loaders operating in the usual way.
-
--   **[Turning Off JTA Transactions](turning_off_jta.html)**
-
-You can configure regions to not participate in any JTA global transaction.
-
-
-
-# Coordinating with External JTA Transactions Managers
-
-Geode can work with the JTA transaction managers of several containers like 
JBoss, WebLogic, GlassFish, and so on.
-
-At startup Geode looks for a TransactionManager 
(`javax.transaction.TransactionManager`) that has been bound to its JNDI 
context. When Geode finds such an external transaction manager, all Geode 
region operations (such as get and put) will participate in global transactions 
hosted by this external JTA transaction manager.
-
-This figure shows the high-level operation of a JTA global transaction whose 
resources include a Geode cache and a database.
-
-
-
-An externally coordinated JTA global transaction is run in the following 
manner:
-
-1.  Each region operation looks up for presence of a global transaction. If 
one is detected, then a Geode transaction is started automatically, and we 
register a `javax.transaction.Synchronization` callback with the external JTA 
transaction manager.
-2.  At transaction commit, Geode gets a `beforeCommit()` callback from the 
external JTA transaction manager. Geode does all locking and conflict detection 
at this time. If this fails, an exception is thrown back to JTA transaction 
manager, which then aborts the transaction.
-3.  After a successful `beforeCommit()`callback, JTA transaction manager asks 
other data sources to commit their transaction.
-4.  Geode then gets a `afterCommit()` callback in which changes 

[37/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/JMX_Architecture.svg
--
diff --git a/geode-docs/images_svg/JMX_Architecture.svg 
b/geode-docs/images_svg/JMX_Architecture.svg
deleted file mode 100644
index f60c097..000
--- a/geode-docs/images_svg/JMX_Architecture.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="106 331 380 360" 
width="380pt" height="30pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 00:09Zjmx 
architectureLayer 1Management and 
Monitoring ToolsJMX Manager Node Distributed SystemOther JMX Clients (JConsole, jvisualvm)
 Managed NodeManaged NodeCMBean ServerDAMBean ServerBMBean ServerY+XAManagerMBeanx="1.9985352" y="9" textLength="6.0029297">Btransform="translate(139 442.875)" fill="black">font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x=".75927734" y="6" textLength="45.023438">Proxied Mbeans font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x="3.0942383" y="13" textLength="40.353516">from Managed font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x="13.765625" y="20" textLength="17.34375">Nodesmarker-end="url(#FilledArrow_Marker_2)" stroke="black" stroke-linecap="round" 
 >stroke-linejoin="round" stroke-width=".23998"/>d="M 159.66 546.75 L 245.34 546.75 C 249.01822 546.75 252 549.73178 252 
 >553.41 L 252 558.09 C 252 5
 61.7682 249.01822 564.75 245.34 564.75 L 159.66 564.75 C 155.98178 564.75 153 
561.7682 153 558.09 L 153 553.41 C 153 549.73178 155.98178 546.75 159.66 546.75 
Z" fill="url(#Obj_Gradient_c)"/>Management ServiceManagement 
ServiceRMI 
ConnectorManagement ServiceCDgfshMemberMBeanMemberMBeanLocal 
MBeansLocal 
MBeansLocal MBeansZYAggregate MBeanMemberMBeanPulseOther JMX Clients (JConsole, jvisualvm)Local view of 
managed node 
onlyRMI 
ConnectorView of 
remote managed node

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/MBeans.svg
--
diff --git a/geode-docs/images_svg/MBeans.svg b/geode-docs/images_svg/MBeans.svg
deleted file mode 100644
index cdfcf6e..000
--- a/geode-docs/images_svg/MBeans.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="54 72 504 450" 
width="42pc" height="450pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 23:57ZmbeanLayer 1DistributedLockServiceMXBeanLocatorMXBeanMemberMXBeanManagerMXBeanDistributedRegionMXBeanDistributedSystemMXBeanJMX Manager NodeRegionMXBeanLockServiceMXBeanManaged NodeDiskStoreMXBean110..N0..10..N10..N0..N0..NAsyncEventQueueMXBeanCacheServerMXBean10..N

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/async_system_queue_conflation.svg
--
diff --git a/geode-docs/images_svg/async_system_queue_conflation.svg 
b/geode-docs/images_svg/async_system_queue_conflation.svg
deleted file mode 100644
index fcc8635..000
--- a/geode-docs/images_svg/async_system_queue_conflation.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="61 349 454 346" 
width="454pt" height="346pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:59ZconflationLayer 1Initial producer queue 
w
 ith conflationentry createKey Bentry updateKey AValue QV1to consumerentry updateKey AValue V2Add entry update to 
queue...entry 
createKey 
Bentry updateKey AValue 
V1to consumerQueue after conflationentry updateKey AValue 
V2entry 
createKey 
Bto consumer

[19/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/management/list_of_mbeans_full.html.md.erb
--
diff --git a/geode-docs/managing/management/list_of_mbeans_full.html.md.erb 
b/geode-docs/managing/management/list_of_mbeans_full.html.md.erb
deleted file mode 100644
index 74fb2bd..000
--- a/geode-docs/managing/management/list_of_mbeans_full.html.md.erb
+++ /dev/null
@@ -1,210 +0,0 @@

-title: JMX Manager MBeans

-
-
-
-This section describes the MBeans that are available on the JMX Manager node.
-
-The JMX Manager node includes all local beans listed under [Managed Node 
MBeans](list_of_mbeans_full.html#topic_48194A5BDF3F40F68E95A114DD702413) and 
the following beans that are available only on the JMX Manager node:
-
--   
[ManagerMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_7B878B450B994514BDFE96571F0D3827)
--   
[DistributedSystemMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_4D7A4C82DD974BB5A5E52B34A6D888B4)
--   
[DistributedRegionMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_48384B091AB846E591F22EEA2770DD36)
--   
[DistributedLockServiceMXBean](list_of_mbeans_full.html#topic_14E3721DD0CF47D7AD8C742DFBE9FB9C__section_9E004D8AA3D24647A5C19CAA1879F0A4)
-
-## ManagerMXBean
-
-Represents the Geode Management layer for the hosting member. Controls the 
scope of management. This MBean provides `start` and `stop` methods to turn a 
managed node into a JMX Manager node or to stop a node from being a JMX 
Manager. For potential managers (`jmx-manager=true` and 
`jmx-manager-start=false`), this MBean is created when a Locator requests it.
-
-**Note:**
-You must configure the node to allow it to become a JMX Manager. See 
[Configuring a JMX 
Manager](jmx_manager_operations.html#topic_263072624B8D4CDBAD18B82E07AA44B6) 
for configuration information.
-
-**MBean Details**
-
-|| 
   |
-|||
-| Scope  | ALL 
   |
-| Proxied| No  
   |
-| Object Name| GemFire:type=Member, 
service=Manager,member=name-or-dist-member-id |
-| Instances Per Node | 1   
   |
-
-See the `org.apache.geode.management.ManagerMXBean` JavaDocs for information 
on available MBean methods and attributes.
-
-## DistributedSystemMXBean
-
-System-wide aggregate MBean that provides a high-level view of the entire 
distributed system including all members (cache servers, peers, locators) and 
their caches. At any given point of time, it can provide a snapshot of the 
complete distributed system and its operations.
-
-The DistributedSystemMXBean provides APIs for performing distributed 
system-wide operations such as backing up all members, shutting down all 
members or showing various distributed system metrics.
-
-You can attach a standard JMX NotificationListener to this MBean to listen for 
notifications throughout the distributed system. See [Geode JMX MBean 
Notifications](mbean_notifications.html) for more information.
-
-This MBean also provides some MBean model navigation APIS. These APIs should 
be used to navigate through all the MBeans exposed by a Geode System.
-
-**MBean Details**
-
-|| |
-||-|
-| Scope  | Aggregate   |
-| Proxied| No  |
-| Object Name| GemFire:type=Distributed,service=System |
-| Instances Per Node | 1   |
-
-See the `org.apache.geode.management.DistributedSystemMXBean` JavaDocs for 
information on available MBean methods and attributes.
-
-## DistributedRegionMXBean
-
-System-wide aggregate MBean of a named region. It provides a high-level view 
of a region for all members hosting and/or using that region. For example, you 
can obtain a list of all members that are hosting the region. Some methods are 
only available for partitioned regions.
-
-**MBean Details**
-
-|| 
|
-||-|
-| Scope  | Aggregate   
|
-| Proxied| No  
|
-| Object Name| 
GemFire:type=Distributed,service=Region,name=regionName |
-| Instances Per Node | 0..N   

[21/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
--
diff --git 
a/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb 
b/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
deleted file mode 100644
index 89e7178..000
--- a/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
+++ /dev/null
@@ -1,79 +0,0 @@

-title:  Disk Store File Names and Extensions

-
-Disk store files include store management files, access control files, and the 
operation log, or oplog, files, consisting of one file for deletions and 
another for all other operations.
-
-
-The next tables describe file names and extensions; they are followed by 
example disk store files.
-
-## File Names
-
-File names have three parts:
-
-**First Part of File Name: Usage Identifier**
-
-| Values   | Used for  
 | Examples   |
-|--|||
-| OVERFLOW | Oplog data from overflow regions and queues only. 
 | OVERFLOWoverflowDS1\_1.crf |
-| BACKUP   | Oplog data from persistent and persistent+overflow regions and 
queues. | BACKUPoverflowDS1.if, BACKUPDEFAULT.if |
-| DRLK\_IF | Access control - locking the disk store.  
 | DRLK\_IFoverflowDS1.lk, DRLK\_IFDEFAULT.lk |
-
-**Second Part of File Name: Disk Store Name**
-
-| Values  | Used for   
   | 
Examples
 |
-|-|---|--|
-| disk store name | Non-default disk stores.   
   | 
name="overflowDS1" DRLK\_IFoverflowDS1.lk, name="persistDS1" 
BACKUPpersistDS1\_1.crf |
-| DEFAULT | Default disk store name, used when persistence or 
overflow are specified on a region or queue but no disk store is named. | 
DRLK\_IFDEFAULT.lk, BACKUPDEFAULT\_1.crf
 |
-
-**Third Part of File Name: oplog Sequence Number**
-
-| Values| Used for 
   | Examples   
  |
-|---|-|--|
-| Sequence number in the format \_n | Oplog data files only. Numbering starts 
with 1. | OVERFLOWoverflowDS1\_1.crf, BACKUPpersistDS1\_2.crf, 
BACKUPpersistDS1\_3.crf |
-
-## File Extensions
-
-| File extension | Used for | Notes

|
-||--|--|
-| if | Disk store metadata  | Stored 
in the first disk-dir listed for the store. Negligible size - not considered in 
size control. |
-| lk | Disk store access control| Stored 
in the first disk-dir listed for the store. Negligible size - not considered in 
size control. |
-| crf| Oplog: create, update, and invalidate operations | 
Pre-allocated 90% of the total max-oplog-size at creation.  
 |
-| drf| Oplog: delete operations | 
Pre-allocated 10% of the total max-oplog-size at creation.  
 |
-| krf| Oplog: key and crf offset information| Created 
after the oplog has reached the max-oplog-size. Used to improve performance at 
startup.  |
-
-Example files for disk stores persistDS1 and overflowDS1:
-
-``` pre
-bash-2.05$ ls -tlra persistData1/
-total 8
--rw-rw-r--   1 person users188 Mar  4 06:17 BACKUPpersistDS1.if
-drwxrwxr-x   2 person users512 Mar  4 06:17 .
--rw-rw-r--   1 person users  0 Mar  4 06:18 BACKUPpersistDS1_1.drf
--rw-rw-r--   1 person users 38 Mar  4 06:18 BACKUPpersistDS1_1.crf
-drwxrwxr-x   8 person users512 Mar  4 06:20 ..
-bash-2.05$
- 
-bash-2.05$ ls -ltra overflowData1/
-total 1028
-drwxrwxr-x 

[07/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/glossary.html.md.erb
--
diff --git a/geode-docs/reference/topics/glossary.html.md.erb 
b/geode-docs/reference/topics/glossary.html.md.erb
deleted file mode 100644
index f039066..000
--- a/geode-docs/reference/topics/glossary.html.md.erb
+++ /dev/null
@@ -1,601 +0,0 @@

-title:  Glossary

-
-This glossary defines terms used in Apache Geode documentation.
-
-## ACK wait threshold
-
-A time-to-wait for message acknowledgment between system members.
-
-## administrative event
-
-See [event](glossary.html#glossary__section_2AF9B98BC1CA402A9F24E552EE9C9ACF).
-
-## API
-
-Application Programming Interface. Geode provides APIs to cached data for Java 
applications.
-
-## application program
-
-A program designed to perform a specific function directly for the user or, in 
some cases, for another application program. Geode applications use the Geode 
application programming interfaces (APIs) to modify cached data.
-
-## attribute
-
-Querying: A named member of a data object. The public fields and methods of an 
object may be accessed as attributes in the context of a query.
-
-Region: See [region 
attributes](glossary.html#glossary__section_7398A81EE9034E7FBDF7B592314586B3).
-
-## attribute path
-
-A sequence of attributes separated by a dot (.), applied to objects where the 
value of each attribute is used to apply the next attribute.
-
-## blocking
-
-A behavior associated with synchronization functions. Blocking behavior is 
exhibited as waiting for a signal to proceed, regardless of how long it takes. 
See also 
[timeout](glossary.html#glossary__section_311C7AE4126A4B1899D6EA1C4E804F57).
-
-## cache
-
-In-memory Geode data storage created by an application or cache server for 
data storage, distribution, and management. This is the point of access for 
Java applications for all caching features, and the only view of the cache that 
is available to the application. Cache creation creates a connection to the 
distributed system. See also 
[local](glossary.html#glossary__section_598D82A75D9842438BB934E01E77266E) and 
[remote](glossary.html#glossary__section_CC864725C0014791805D2549D87DA545).
-
-## cache-local
-
-Residing or occurring in the local cache.
-
-## cache.xml
-
-Common name for the XML file that declares the initial configuration of a 
cache. This file is used to customize the behavior of the Geode cache server 
process and can be used by any Java application. Applications can also 
configure the cache through the Geode Java APIs. You can give this file any 
name.
-
-## cache event
-
-See [event](glossary.html#glossary__section_2AF9B98BC1CA402A9F24E552EE9C9ACF).
-
-## cache listener
-
-User-implemented plug-in for receiving and handling region entry events. A 
region’s cache listener is called after an entry in the local cache is 
modified. See also [cache 
writer](glossary.html#glossary__section_40FFA1BD5E4A4E3084AE8B257C612EDE).
-
-## cache loader
-
-User-implemented plug-in for loading data into a region. A region’s cache 
loader is used to load data that is requested of the region but is not 
available in the distributed system. For a distributed region, the loader that 
is used can be in a different cache from the one where the data-request 
operation originated. See also 
[netSearch](glossary.html#glossary__section_B9B118509831405D9AB4069503119DFB) 
and 
[netLoad](glossary.html#glossary__section_BFFF4BF9D6414AA392F7AEAC1256C112).cache
 misses, where a requested key is not present or has a null value in the local 
cache.
-
-## cache miss
-
-The situation where a key’s value is requested from a cache and the 
requested key is not present or has a null value. Geode responds to cache 
misses in various ways, depending on the region and system configuration. For 
example, a client region goes to its servers to satisfy cache misses. A region 
with local scope uses its data loader to load the value from an outside data 
source, if a loader is installed on the region.
-
-## cache 
server
-
-A long-lived, configurable Geode distributed system member process that can 
service client connections.
-
-## cache 
transaction
-
-A native Geode transaction, managed by Geode and not by JTA. This type of 
transaction operates only on data available from the Geode cache in the local 
member. See also 
[JTA](glossary.html#glossary__section_2B4ADA311CA946839F3E8F3B071D4E74) and 
[global 
transaction](glossary.html#glossary__section_CDA3C2530A74433CBE0204D588C237AC).
-
-## cache writer
-
-User-implemented plug-in intended for synchronizing the cache with an outside 
data source. A region’s cache writer is a synchronous listener to cache data 
events. The cache writer has the ability to abort a data modification. See also 
[cache 
listener](glossary.html#glossary__section_688E118C48B246AF9D2AAB64AE9481D4) and 

[11/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/chapter_overview_cache_xml.html.md.erb
--
diff --git a/geode-docs/reference/topics/chapter_overview_cache_xml.html.md.erb 
b/geode-docs/reference/topics/chapter_overview_cache_xml.html.md.erb
deleted file mode 100644
index 02e54f1..000
--- a/geode-docs/reference/topics/chapter_overview_cache_xml.html.md.erb
+++ /dev/null
@@ -1,30 +0,0 @@

-title:  cache.xml

-
-Use the cache.xml file to set up general cache facilities and behavior and to 
create and initialize cached data regions. These sections document cache.xml 
requirements; provide hierarchical diagrams of `` and `
 `elements; and describe the function of each element.
-
-**Note:**
-You can configure most elements of the cache.xml file and apply it to your 
entire cluster by using the 
[gfsh](../../tools_modules/gfsh/chapter_overview.html) and [cluster 
configuration service](../../configuring/cluster_config/gfsh_persist.html). See 
[gfsh 
Limitations](../../configuring/cluster_config/gfsh_persist.html#concept_r22_hyw_bl__section_bn3_23p_y4)
 for a list of items you cannot configure in gfsh and must still configure in 
cache.xml.
-
--   **[cache.xml Quick Reference](../../reference/topics/elements_ref.html)**
-
-This section documents cache.xml file requirements and variables. It also 
points you to specific element sections for server, client, and WAN 
configuration.
-
--   **[cache Element 
Hierarchy](../../reference/topics/cache-elements-list.html)**
-
-This section shows the hierarchy of `` element sub-elements that 
you use to configure Geode caches and servers.
-
--   **[cache Element 
Reference](../../reference/topics/cache_xml.html#cache_xml_cache)**
-
-This section documents the `cache.xml` sub-elements used for Geode server 
configuration. All elements are sub-elements of the `` element.
-
--   **[client-cache Element 
Hierarchy](../../reference/topics/client-cache-elements-list.html)**
-
-This section shows the hierarchy of `` element sub-elements 
that you use to configure Geode caches and clients.
-
--   **[client-cache Element 
Reference](../../reference/topics/client-cache.html)**
-
-This section documents all `cache.xml` elements that you use to configure 
Geode clients. All elements are sub-elements of the `` element.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/chapter_overview_regionshortcuts.html.md.erb
--
diff --git 
a/geode-docs/reference/topics/chapter_overview_regionshortcuts.html.md.erb 
b/geode-docs/reference/topics/chapter_overview_regionshortcuts.html.md.erb
deleted file mode 100644
index dec958d..000
--- a/geode-docs/reference/topics/chapter_overview_regionshortcuts.html.md.erb
+++ /dev/null
@@ -1,90 +0,0 @@

-title:  Region Shortcuts

-
-This topic describes the various region shortcuts you can use to configure 
Geode regions.
-
-Region shortcuts are groupings of pre-configured attributes that define the 
characteristics of a region. You can use a region shortcut as a starting point 
when configuring regions and you can add additional configurations to customize 
your application. To reference a region shortcut in a Geode `cache.xml` file, 
use the `refid` attribute of the `` element. For example:
-
-``` pre
-
-```
-
-You can override the default values and add additional configurations within a 
`` element of the `cache.xml` file. For example, the 
following configuration overrides the local-max-memory setting and adds the recovery-delay attribute:
-
-``` pre
-
-
-
-
-
-```
-
-You can also create your own, named region shortcuts for common custom 
configurations. See [Region Shortcuts and Custom Named Region 
Attributes](../../basic_config/data_regions/region_shortcuts.html).
-
-To configure a region using the gfsh command-line tool, specify the shortcut 
name with the `--type` argument. For example:
-
-``` pre
-gfsh>create region --name=myRegion --type=PARTITION_REDUNDANT
-```
-
-**Note:**
-If you change the cache.xml file that defines a region, you must restart the 
member before the changes take effect.
-
-For more information about configuring regions, see [Data Region 
Management](../../basic_config/data_regions/managing_data_regions.html#data_regions).
-
-For more information about using the various types of Geode regions and when 
to use them, see [Region 
Types](../../developing/region_options/region_types.html#region_types).
-
--   **[Region Shortcuts Quick 
Reference](../../reference/topics/region_shortcuts_table.html)**
-
-This section provides a quick reference for all region shortcuts.
-
--   
**[LOCAL](../../reference/topics/region_shortcuts_reference.html#reference_w2h_3cd_lk)**
-
--   

[26/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/server_grouping.svg
--
diff --git a/geode-docs/images_svg/server_grouping.svg 
b/geode-docs/images_svg/server_grouping.svg
deleted file mode 100644
index 15eab1f..000
--- a/geode-docs/images_svg/server_grouping.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="122 212 373 301" 
width="373pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:30Zserver_groupingLayer 
1Server #1
 Client #1Region: Portfoliosconnection 
poolServer #2Region: ProductsRegion: Portfolioslistening on 
10.80.100.1 :  40404group: 
Portfolioslistening on 10.80.100.2 :  40404group: 
Productslocator at lucy : 
4server-group: PortfoliosClient 
#2Region: Productsconnection 
poollocator 
at
  lucy : 4server-group: ProductsLocatorlistening on lucy : 
4Portfolios: 
10.80.100.1 : 40404Products: 10.80.100.2 : 
40404

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/images_svg/transactions_partitioned_1.svg
--
diff --git a/geode-docs/images_svg/transactions_partitioned_1.svg 
b/geode-docs/images_svg/transactions_partitioned_1.svg
deleted file mode 100644
index c101378..000
--- a/geode-docs/images_svg/transactions_partitioned_1.svg
+++ /dev/null
@@ -1,3 +0,0 @@
-
-http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
-http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="5 95 562 274" 
width="562pt" height="274pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:50Zpartition-1Layer 1Member 
(M1)CacheXYRegion AZJava ApplicationTransaction T1primary datasecondary dataWWT1 local 
eventsMember (M2)CacheXYRegion AZTransaction T2secondary dataprimary 
dataWT2 local 
eventsYZT1T2

[13/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/cache-elements-list.html.md.erb
--
diff --git a/geode-docs/reference/topics/cache-elements-list.html.md.erb 
b/geode-docs/reference/topics/cache-elements-list.html.md.erb
deleted file mode 100644
index e643a84..000
--- a/geode-docs/reference/topics/cache-elements-list.html.md.erb
+++ /dev/null
@@ -1,168 +0,0 @@

-title: "cache Element Hierarchy"

-
-This section shows the hierarchy of `` element sub-elements that you 
use to configure Geode caches and servers.
-
-For details, see [cache Element 
Reference](cache_xml.html#cache_xml_cache).
-
-``` pre
-
-   
-  
-  
-   
-  
- 
- 
- 
-   
-  
-  
-   
-  
-   
-  
-  
- 
- 
-
-
-   
-  
-  
-  
-  
-  
- 
- 
-   
-  
-  
-   
-  
- 
-   
-  
- 
- 
-
-
-   
-  
-  
-  
- 
-
-   
-   
-  
-  
-  
- 
-
-   
-   
-  
-  
-  
- 
-
-   
-   
-  
-  
-  
- 
-
-   
-   
-  
-  
-  
- 
-
-   
-  
-  
- 
-
-   
-  
-  
- 

[06/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/region_shortcuts_reference.html.md.erb
--
diff --git a/geode-docs/reference/topics/region_shortcuts_reference.html.md.erb 
b/geode-docs/reference/topics/region_shortcuts_reference.html.md.erb
deleted file mode 100644
index f3d9ca9..000
--- a/geode-docs/reference/topics/region_shortcuts_reference.html.md.erb
+++ /dev/null
@@ -1,1482 +0,0 @@

-title:  Region Shortcuts Reference

-
-This topic describes the various region shortcuts you can use to configure 
Geode regions.
-
-## LOCAL
-
-### Description
-
-A region configured with the LOCAL 
region shortcut is scoped only to its JVM and is not visible to other peer 
members. The region does not distribute data and operations to other caches.
-
-For more information, see:
-
--   [Local 
Regions](../../developing/region_options/region_types.html#region_types__section_A8150BDBC74E4019B1942481877A4370)
--   [RegionShortcuts for Peers and 
Servers](../../basic_config/data_regions/region_shortcuts.html#region_shortcuts__section_D0975C76572E41F79C1A6EE7CF371251)
-
-### Default Attributes
-
-Region Attributes
-
-||   |
-||---|
-| scope: | local |
-| data-policy: | NORMAL |
-
-### gfsh Command Example
-
-``` pre
-gfsh>create region --name=myLOCALregion --type=LOCAL
-```
-
-``` pre
-gfsh>describe region --name=myLOCALregion
-..
-Name: myLOCALregion
-Data Policy : normal
-Hosting Members : server1
-  server2
-
-Non-Default Attributes Shared By Hosting Members  
-
- Type  |Name | Value
--- | --- | --
-Region | data-policy | NORMAL
-   | size| 0
-```
-
-### XML Definition of LOCAL
-
-``` pre
-
-   
-
-```
-
-## LOCAL\_HEAP\_LRU
-
-### Description
-
-A region configured with the LOCAL\_HEAP\_LRU region shortcut is scoped to its JVM and is 
not visible to other peer members. The region does not distribute data and 
operations to other caches. The region destroys the least recently used entries 
when it detects that the JVM is running low on memory.
-
-For more information, see:
-
--   [Eviction](../../developing/eviction/chapter_overview.html)
--   [Local 
Regions](../../developing/region_options/region_types.html#region_types__section_A8150BDBC74E4019B1942481877A4370)
-
-### Default Attributes
-
-Region Attributes
-
-|||
-|||
-| scope: |  local |
-| data-policy: | NORMAL  |
-
-Eviction Attributes
-
-| | |
-|-|-|
-| eviction-algorithm: | lru-heap-percentage |
-| eviction-action:| local-destroy   |
-
-### gfsh Command Example
-
-``` pre
-gfsh>create region --name=myLHLregion --type=LOCAL_HEAP_LRU
-```
-
-``` pre
-gfsh>describe region --name=myLHLregion
-...
-Name: myLHLregion
-Data Policy : normal
-Hosting Members : server1
-  server2
-
-Non-Default Attributes Shared By Hosting Members  
-
-  Type   |Name| Value
- | -- | ---
-Region   | data-policy| NORMAL
- | size   | 0
-Eviction | eviction-algorithm | lru-heap-percentage
- | eviction-action| local-destroy
-```
-
-### XML Definition of LOCAL\_HEAP\_LRU
-
-``` pre
-
-   
-  
-
-  
-   org.apache.geode.internal.size.SizeClassOnceObjectSizer
-  
-
-  
-   
-
-```
-
-## LOCAL\_OVERFLOW
-
-### Description
-
-A region configured with the LOCAL\_OVERFLOW region shortcut is scoped only to its JVM and 
is not visible to other peer members. The region does not distribute data and 
operations to other caches. The region moves the values of entries to disk when 
it detects that the JVM is running low on memory.
-
-For more information, see:
-
--   [Persistence and 
Overflow](../../developing/storing_data_on_disk/chapter_overview.html)
--   [Local 
Regions](../../developing/region_options/region_types.html#region_types__section_A8150BDBC74E4019B1942481877A4370)
--   [Eviction](../../developing/eviction/chapter_overview.html)
-
-### Default Attributes
-
-Region Attributes
-
-|||
-|||
-| scope: |  local |
-| data-policy: | NORMAL |
-
-Eviction Attributes
-
-| | |
-|-|-|
-| eviction-algorithm: | lru-heap-percentage |
-| eviction-action:| overflow-to-disk|
-
-### gfsh Command Example
-
-``` pre
-gfsh>create region --name=myLOregion --type=LOCAL_OVERFLOW
-```
-
-``` pre
-gfsh>describe region --name=myLOregion
-...
-Name: myLOregion
-Data Policy : normal
-Hosting Members : server1
-  server2
-
-Non-Default 

[12/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/cache_xml.html.md.erb
--
diff --git a/geode-docs/reference/topics/cache_xml.html.md.erb 
b/geode-docs/reference/topics/cache_xml.html.md.erb
deleted file mode 100644
index a1969d4..000
--- a/geode-docs/reference/topics/cache_xml.html.md.erb
+++ /dev/null
@@ -1,3090 +0,0 @@

-title: "cache Element Reference"

-
-
-
-This section documents the `cache.xml` sub-elements used for Geode server 
configuration. All elements are sub-elements of the `` element.
-
-For Geode client configuration, see [client-cache Element 
Reference](client-cache.html#cc-client-cache).
-
-**API**:`org.apache.geode.cache.CacheFactory`
-
-
-
-
-Table 1. cache Element 
Attributes
-
-
-
-
-
-
-
-Attribute
-Description
-Default
-
-
-
-
-copy-on-read
-Boolean indicating whether entry value retrieval methods return direct 
references to the entry value objects in the cache (false) or copies of the 
objects (true).
-False
-
-
-is-server
-Boolean indicating whether this member is a cache server.
-False
-
-
-lock-timeout
-The timeout, in seconds, for implicit object lock requests. This 
setting affects automatic locking only, and does not apply to manual locking. 
If a lock request does not return before the specified timeout period, it is 
cancelled and returns with a failure.
-60
-
-
-lock-lease
-The timeout, in seconds, for implicit and explicit object lock leases. 
This affects both automatic locking and manual locking. Once a lock is 
obtained, it can remain in force for the lock lease time period before being 
automatically cleared by the system.
-120
-
-
-message-sync-interval
-Used for client subscription queue synchronization when this member 
acts as a server to clients and server redundancy is used. Sets the frequency 
(in seconds) at which the primary server sends messages to its secondary 
servers to remove queued events that have already been processed by the 
clients.
-1
-
-
-search-timeout
-How many seconds a netSearch operation 
can wait for data before timing out. You may want to change this based on your 
knowledge of the network load or other factors.
-300
-
-
-
-
-Table 1. cache Element Attributes
-
-**Example:**
-
-``` pre
-
-  
-  
-
-
-  
-
-  cacheRunner.StringLoader
-
-  
-  cacheRunner.LoggingCacheListener
-
-  
-
-  
-
-```
-
-## cache-transaction-manager
-
-Specifies a transaction listener.
-
-**API:** `CacheTransactionManager`
-
-**Example:**
-
-``` pre
-
-   
- 
-   com.company.data.MyTransactionListener
-   
- jdbc:cloudscape:rmi:MyData
-   
- 
- ...  
- 
-   com.company.data.MyTransactionWriter
-   
- jdbc:cloudscape:rmi:MyData
-   
-   
- 
-.. .
-
-```
-
-## transaction-listener
-
-When a transaction ends, its thread calls the TransactionListener to perform 
the appropriate follow-up for successful commits, failed commits, or voluntary 
rollbacks.
-
-Specify the Java class and its initialization parameters with the 
`` and `` sub-elements. See [class-name and 
parameter](#class-name_parameter).
-
-## transaction-writer
-
-When you commit a transaction, a TransactionWriter can perform additional 
tasks, including aborting the transaction.
-
-Specify the Java class and its initialization parameters with the 
`` and `` sub-elements. See [class-name and 
parameter](#class-name_parameter).
-
-## dynamic-region-factory
-
-The `` element configures a dynamic region factory for 
this cache. You can use this element to dynamically create regions in your 
application code. Use the createDynamicRegion() method of the org.apache.geode.cache.DynamicRegionFactory class in your Java 
code to dynamically create regions.
-
-**Note:**
-You can not use this element to dynamically create *partitioned* regions.
-
-We recommend that you use functions to dynamically create regions. See 
[Creating Regions 
Dynamically](../../developing/region_options/dynamic_region_creation.html).
-
-The optional `` sub-element specifies the directory to store the 
persistent files that are used for dynamic region bookkeeping. It defaults to 
the current directory.
-
-Set the `pool-name` attribute to set the name of the connection pool used by 
client applications in a client/server cache configuration. Do not specify the 
`pool-name` attribute in servers or peers.
-
-**API:** `org.apache.geode.cache.DynamicRegionFactory`
-
-
-
-| Attribute | Description  
  | 
Default |
-|---||-|
-| disable-persist-backup| When set to false, the factory is persisted on 

[14/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/statistics/statistics_list.html.md.erb
--
diff --git a/geode-docs/reference/statistics/statistics_list.html.md.erb 
b/geode-docs/reference/statistics/statistics_list.html.md.erb
deleted file mode 100644
index f366faf..000
--- a/geode-docs/reference/statistics/statistics_list.html.md.erb
+++ /dev/null
@@ -1,1276 +0,0 @@

-title: Geode Statistics List

-
-
-
-
-This section describes the primary statistics gathered by Geode when 
statistics are enabled.
-
-All statistics gathering requires the `gemfire.properties` 
`statistic-sampling-enabled` in `gemfire.properties` file to be true. 
Statistics that use time require the `gemfire.properties` 
`enable-time-statistics` to be true.
-
-Performance statistics are collected for each Java application or cache server 
that connects to a distributed system.
-
--   **[Cache Performance 
(CachePerfStats)](#section_DEF8D3644D3246AB8F06FE09A37DC5C8)**
-
--   **[Cache Server 
(CacheServerStats)](#section_EF5C2C59BFC74FFB8607F9571AB9A471)**
-
--   **[Client-Side Notifications 
(CacheClientUpdaterStats)](#section_B08C0783BBF9489E8BB48B4AEC597C62)**
-
--   **[Client-to-Server Messaging Performance 
(ClientStats)](#section_04B7D7387E584712B7710B5ED1E876BB)**
-
--   **[Client Connection Pool 
(PoolStats)](#section_6C247F61DB834C079A16BE92789D4692)**
-
--   **[Continuous Querying 
(CQStatistics)](#section_66C0E7748501480B85209D57D24256D5)**
-
--   **[Delta Propagation 
(DeltaPropagationStatistics)](#section_D4ABED3FF94245C0BEE0F6FC9481E867)**
-
--   **[Disk Space Usage 
(DiskDirStatistics)](#section_6C2BECC63A83456190B029DEDB8F4BE3)**
-
--   **[Disk Usage and Performance 
(DiskRegionStatistics)](#section_983BFC6D53C74829A04A91C39E06315F)**
-
--   **[Distributed System Messaging 
(DistributionStats)](#section_ACB4161F10D64BC0B15871D003FF6FDF)**
-
--   **[Distributed Lock Services 
(DLockStats)](#section_78D346A580724E1EA645E31626EECE40)**
-
--   **[Function Execution 
(FunctionServiceStatistics)](#section_5E211DDB0E8640689AD0A4659511E17A)**
-
--   **[Gateway Queue 
(GatewayStatistics)](#section_C4199A541B1F4B82B6178C416C0FAE4B)**
-
--   **[Indexes (IndexStats)](#section_86A61860024B480592DAC67FFB882538)**
-
--   **[JVM Performance](#section_607C3867602E410CAE5FAB26A7FF1CB9)**
-
--   **[Locator 
(LocatorStatistics)](#section_C48B654F973E4B44AD825D459C23A6CD)**
-
--   **[Off-Heap (OffHeapMemoryStats)](#topic_ohc_tjk_w5)**
-
--   **[Operating System Statistics - 
Linux](#section_923B28F01BC3416786D3AFBD87F22A5E)**
-
--   **[Partitioned Regions 
(PartitionedRegionpartitioned\_region\_nameStatistics)](#section_35AC170770C944C3A336D9AEC2D2F7C5)**
-
--   **[Region Entry Eviction – Count-Based 
(LRUStatistics)](#section_374FBD92A3B74F6FA08AA23047929B4F)**
-
--   **[Region Entry Eviction – Size-based 
(LRUStatistics)](#section_3D2AA2BCE5B6485699A7B6ADD1C49FF7)**
-
--   **[Server Notifications for All Clients 
(CacheClientNotifierStatistics)](#section_5362EF9AECBC48D69475697109ABEDFA)**
-
--   **[Server Notifications for Single Client 
(CacheClientProxyStatistics)](#section_E03865F509E543D9B8F9462B3DA6255E)**
-
--   **[Server-to-Client Messaging Performance 
(ClientSubscriptionStats)](#section_3AB1C0AA55014163A2BBF68E13D25E3A)**
-
--   **[Statistics Collection 
(StatSampler)](#section_55F3AF6413474317902845EE4996CC21)**
-
-## Cache Performance (CachePerfStats)
-
-Statistics for the Geode cache. These can be used to determine the type and 
number of cache operations being performed and how much time they consume.
-
-Regarding Geode cache transactions, transaction-related statistics are 
compiled and stored as properties in the CachePerfStats statistic resource. 
Because the transaction’s data scope is the cache, these statistics are 
collected on a per-cache basis.
-
-The primary statistics are:
-
-| Statistic| Description   










   |

[05/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/rest_apps/develop_rest_apps.html.md.erb
--
diff --git a/geode-docs/rest_apps/develop_rest_apps.html.md.erb 
b/geode-docs/rest_apps/develop_rest_apps.html.md.erb
deleted file mode 100644
index fff34d5..000
--- a/geode-docs/rest_apps/develop_rest_apps.html.md.erb
+++ /dev/null
@@ -1,666 +0,0 @@

-title: Developing REST Applications

-
-
-
-This section provides guidelines on writing REST client applications for Geode.
-
-You can browse, query, update and delete data stored in your Geode deployment. 
You can also manage and execute pre-deployed functions on Geode members.
-
--   **[Working with 
Regions](../rest_apps/develop_rest_apps.html#topic_qhs_f25_m4)**
-
-The Geode REST APIs provide basic CRUD (create, read, update and delete) 
operations for data entries stored in your regions.
-
--   **[Working with 
Queries](../rest_apps/develop_rest_apps.html#topic_fcn_g25_m4)**
-
-Geode supports the use of queries to extract data from its regions. Using 
REST APIs, you can create and execute either prepared or ad-hoc queries on 
Geode regions. You can also update and delete prepared queries.
-
--   **[Working with 
Functions](../rest_apps/develop_rest_apps.html#topic_rbc_h25_m4)**
-
-Geode REST APIs support the discovery and execution of predefined Geode 
functions on your cluster deployments.
-
-## Working with Regions
-
-The Geode REST APIs provide basic CRUD (create, read, update and delete) 
operations for data entries stored in your regions.
-
-Regions are the resources of the Geode REST API. Each region represents a 
resource or a collection of resources.
-
-You cannot create or delete the regions themselves with the REST APIs, but you 
can work with the data stored within predefined Geode regions. Use the 
[gfsh](../tools_modules/gfsh/chapter_overview.html) command utility to add, 
configure or delete regions in your Geode deployment. Any additions or 
modifications to regions made through `gfsh` are then accessible by the REST 
APIs.
-
-## Listing Available Regions
-
-The main resource endpoint to the Geode API is [GET 
/gemfire-api/v1](get_regions.html#topic_itv_mg5_m4). Use this endpoint to 
discover which regions are available in your cluster.
-
-Example call:
-
-``` pre
-curl -i http://localhost:7070/gemfire-api/v1
-```
-
-Example response:
-
-``` pre
-Accept: application/json
-Response Payload: application/json
-
-200 OK
-Server: Apache-Coyote/1.1
-Location: http://localhost:7070/gemfire-api/v1
-Content-Type: application/json
-Transfer-Encoding: chunked
-Date: Sat, 18 Jan 2014 20:05:47 GMT
-{
-"regions": [
-{
-"name": "customers",
-"type": "REPLICATE",
-"key-constraint": "java.lang.String",
-"value-constraint": "org.apache.geode.pdx.PdxInstance"
-},
-{
-"name": "items",
-"type": "REPLICATE",
-"key-constraint": null,
-"value-constraint": null
-},
-{
-"name": "orders",
-"type": "PARTITION",
-"key-constraint": null,
-"value-constraint": null
-},
-{
-"name": "primitiveKVStore",
-"type": "PARTITION",
-"key-constraint": null,
-"value-constraint": null
-},
-{
-"name": "empty_region",
-"type": "EMPTY",
-"key-constraint": "java.lang.String",
-"value-constraint": "org.apache.geode.pdx.PdxInstance"
-}
-]
-}
-```
-
-Each region listed in the response includes the following region attributes:
-
--   **name**. Name of the region.
--   **type**. Type of region. For example, REPLICATE, PARTITION, or EMPTY. See 
[Region Types](../developing/region_options/region_types.html#region_types) for 
more information.
--   **key-constraint**. If defined, the fully qualified class name of the 
key's type. Otherwise, null.
--   **value-constraint**. If defined, the fully qualified class name of the 
value's type. Otherwise, null.
-
-If no resources (regions) are available in the cluster, the call returns a 404 
NOT FOUND error.
-
-## Reading Region Data
-
-You can read data from a region by using any of the following REST-enabled 
mechanisms:
-
--   **GET /gemfire-api/v1/{region}?limit=ALL** - Read all entries in a region
--   **GET /gemfire-api/v1/{region}?limit=*N*** - Read a limited number of 
entries in a region
--   **GET /gemfire-api/v1/{region}/keys** - List all keys in a region
--   **GET /gemfire-api/v1/{region}/{keys}** - Read data for specific key or 
keys in a region
-
-**Reading Entries**
-
-To read entries in a region, use the following REST endpoint:
-
-``` pre
-GET /gemfire-api/v1/{region}?[limit={|ALL}]
-```
-
-For example:
-
-``` pre
-http://localhost:7070/gemfire-api/v1/items
-```
-
-To read all entries in the region, 

[10/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/client-cache.html.md.erb
--
diff --git a/geode-docs/reference/topics/client-cache.html.md.erb 
b/geode-docs/reference/topics/client-cache.html.md.erb
deleted file mode 100644
index 8c42c16..000
--- a/geode-docs/reference/topics/client-cache.html.md.erb
+++ /dev/null
@@ -1,2666 +0,0 @@

-title: "client-cache Element Reference"

-
-
-This section documents all `cache.xml` elements that you use to configure 
Geode clients. All elements are sub-elements of the `` element.
-
-For Geode server configuration, see [cache Element 
Reference](cache_xml.html).
-
-API: `org.apache.geode.cache.client.ClientCacheFactory` and `PoolFactory` 
interfaces.
-
-
-
-
-Table 1. Attributes of 
client-cache
-
-
-
-
-
-
-
-Attribute
-Definition
-Default
-
-
-
-
-copy-on-read
-Boolean indicating whether entry value retrieval methods return direct 
references to the entry value objects in the cache (false) or copies of the 
objects (true).
-False
-
-
-
-
-: Table 1. Attributes of client-cache
-
-**Example:**
-
-``` pre
-
-  
-
-  
-   
-  
-
-
-  
-
-  
-
-```
-
-## cache-transaction-manager
-
-Specifies a transaction listener.
-
-**API:** `CacheTransactionManager`
-
-**Example:**
-
-``` pre
-
-   
- 
-   com.company.data.MyTransactionListener
-   
- jdbc:cloudscape:rmi:MyData
-   
- 
- ...  
- 
-   com.company.data.MyTransactionWriter
-   
- jdbc:cloudscape:rmi:MyData
-   
-   
- 
-.. .
-
-```
-
-## transaction-listener
-
-When a transaction ends, its thread calls the TransactionListener to perform 
the appropriate follow-up for successful commits, failed commits, or voluntary 
rollbacks.
-
-Specify the Java class and its initialization parameters with the 
`` and `` sub-elements. See [class-name and 
parameter](cache_xml.html#class-name_parameter).
-
-## transaction-writer
-
-When you commit a transaction, a TransactionWriter can perform additional 
tasks, including aborting the transaction.
-
-Specify the Java class and its initialization parameters with the 
`` and `` sub-elements. See [class-name and 
parameter](cache_xml.html#class-name_parameter).
-
-## pool
-
-Use for client caches. Defines a client's server pool used to communicate with 
servers running in a different distributed system.
-
-**API:** `org.apache.geode.cache.client.PoolFactory`
-
-
-
-
-Table 2. Attributes
-
-
-
-
-
-
-
-Attribute
-Description
-Default
-
-
-
-
-free-connection-timeout
-Amount of time a thread will wait to get a pool connection before timing 
out with an exception. This timeout keeps threads from waiting indefinitely 
when the pool’s max-connections has been 
reached and all connections in the pool are in use by other threads.
-1
-
-
-idle-timeout
-Maximum time, in milliseconds, a pool connection can stay open without 
being used when there are more than min-connections in the pool. Pings over the connection do not 
count as connection use. If set to -1, there is no idle timeout.
-5000
-
-
-load-conditioning-interval
-Amount of time, in milliseconds, a pool connection can remain open before 
being eligible for silent replacement to a less-loaded server.
-30
-(5 minutes)
-
-
-max-connections
-Maximum number of pool connections the pool can create. If the maximum 
connections are in use, an operation requiring a client-to-server connection 
blocks until a connection becomes available or the free-connection-timeout is reached. If set to -1, there is no 
maximum. The setting must indicate a cap greater than min-connections.
-
-**Note:**
-If you need to use this to cap your pool connections, you should disable 
the pool attribute pr-single-hop-enabled. 
Leaving single hop enabled can increase thrashing and lower performance.
-
--1
-
-
-min-connections
-Minimum number of pool connections to keep available at all times. Used to 
establish the initial connection pool. If set to 0 (zero), no connection is 
created until an operation requires it. This number is the starting point, with 
more connections added later as needed, up to the max-connection setting. The setting must be an integer greater 
than or equal to 0.
-1
-
-
-multiuser-authentication
-Used for installations with security where you want to accommodate 
multiple users within a single client. If set to true, the pool provides 
authorization for multiple user instances in the same client application, and 
each user accesses the cache through its own RegionService instance. If false, the client either uses no 
authorization or just provides credentials for the single client process.
-false
-
-
-name
-Name of this pool. Used in the client region pool-name to assign this pool 
to a region in the client cache.
-
-**Note:**
-This is a required property with no default setting.
-
-none
-
-
-ping-interval
-How often to 

[09/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/elements_ref.html.md.erb
--
diff --git a/geode-docs/reference/topics/elements_ref.html.md.erb 
b/geode-docs/reference/topics/elements_ref.html.md.erb
deleted file mode 100644
index 9b13fab..000
--- a/geode-docs/reference/topics/elements_ref.html.md.erb
+++ /dev/null
@@ -1,100 +0,0 @@

-title:  cache.xml Quick Reference

-
-This section documents cache.xml file requirements and variables. It also 
points you to specific element sections for server, client, and WAN 
configuration.
-
--   [Cache XML 
Requirements](#topic_7B1CABCAD056499AA57AF3CFDBF8ABE3__section_A6B050113DCC4D12A6A9C0F250527AF8)
--   [Variables in 
cache.xml](#topic_7B1CABCAD056499AA57AF3CFDBF8ABE3__section_5DBA12F9FC08406AAD5557E13A3DEDF2)
--   [Configuration Quick 
Reference](elements_ref.html#topic_7B1CABCAD056499AA57AF3CFDBF8ABE3__section_2076DDF1F0464CF8894B42ABC32AE4CB)
-
-## Cache XML Requirements
-
-The cache.xml file has these requirements:
-
--   The contents must conform to the XML schema definition provided in 
cache-1.0.xsd. The schema definition file is available in the product 
distribution at `$GEMFIRE/schemas/geode.apache.org/schema/cache/cache-1.0.xsd`.
--   The file must include a cache schema declaration of one of the 
following forms:
--   Server or peer cache:
-
-``` pre
-
-http://geode.incubator.apache.org/schema/cache;
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
-xsi:schemaLocation="http://geode.incubator.apache.org/schema/cache 
http://geode.incubator.apache.org/schema/cache/cache-1.0.xsd;
-version="1.0">
-...
-
-```
-
--   Client cache:
-
-``` pre
-
-http://geode.incubator.apache.org/schema/cache;
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
-xsi:schemaLocation="http://geode.incubator.apache.org/schema/cache 
http://geode.incubator.apache.org/schema/cache/cache-1.0.xsd;
-version="1.0">
-...
-
-```
-
--   Any class name specified in the file **must have a public zero-argument 
constructor** and must implement the `org.apache.geode.cache.Declarable` 
interface. Parameters declared in the XML for the class are passed to the class 
init method.
-
-## Variables in cache.xml
-
-You can use variables in the `cache.xml` to customize your settings without 
modifying the XML file.
-
-Set your variables in Java system properties when you start your cache server 
or application process.
-
-Example cache.xml with variables and the gfsh `start server` command that sets 
the variables:
-
-``` pre
-
-http://geode.incubator.apache.org/schema/cache;
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
-xsi:schemaLocation="http://geode.incubator.apache.org/schema/cache 
http://geode.incubator.apache.org/schema/cache/cache-1.0.xsd;
-version="1.0">
-  
-  
-
-  
-
-```
-
-``` pre
-gfsh>start server --name=server2 --cache-xml-file=cache.xml --J=-DPORT=30333 
--J=-DMAXCNXS=77
-```
-
-## Configuration Quick Reference
-
-To configure cache servers, clients, and WAN topologies, see the following 
sections:
-
--   Server Configuration
-
--   [cache Element Reference](cache_xml.html#cache_xml_cache)
--   [cache-server](cache_xml.html#cache-server)
--   [region](cache_xml.html#region)
--   [region-attributes](cache_xml.html#region-attributes)
-
-You can set the same server configuration properties using the `org.apache.geode.cache.server.CacheServer` and 
`org.apache.geode.cache.Cache` interfaces. 
For detailed information, see the online Java API documentation.
-
--   Client Configuration
-
--   [client-cache Element 
Reference](client-cache.html#cc-client-cache)
--   [pool](client-cache.html#cc-pool)
--   [region](client-cache.html#cc-region)
-
-You can set the same client configuration properties using the `org.apache.geode.cache.clientClientCache` and 
`Pool` interfaces. For detailed 
information, see the online Java API documentation.
-
--   Multi-site (WAN) Configuration and Asynchronous Event Queue Configuration
-
--   
[gateway-sender](../../reference/topics/gfe_cache_xml.html#gateway-sender)
--   
[gateway-receiver](../../reference/topics/gfe_cache_xml.html#gateway-receiver)
--   
[async-event-queue](../../reference/topics/gfe_cache_xml.html#id_zrr_scq_rr)
-
-The gateway sender and receiver APIs in `org.apache.geode.cache.util` provide corresponding getter and 
setter methods for these attributes.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/reference/topics/gemfire_properties.html.md.erb
--
diff --git a/geode-docs/reference/topics/gemfire_properties.html.md.erb 

[04/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/rest_apps/rest_examples.html.md.erb
--
diff --git a/geode-docs/rest_apps/rest_examples.html.md.erb 
b/geode-docs/rest_apps/rest_examples.html.md.erb
deleted file mode 100644
index 3994ff0..000
--- a/geode-docs/rest_apps/rest_examples.html.md.erb
+++ /dev/null
@@ -1,691 +0,0 @@

-title: Sample REST Applications

-
-
-
-
-This section provides examples that illustrate how multiple clients, both REST 
and native, can access the same Geode region data.
-
-**Note:**
-You must set PDX read-serialized to true when starting the cache server to 
achieve interoperability between different clients. See [Setup and 
Configuration](setup_config.html#topic_e21_qc5_m4) for instructions on starting 
up REST-enabled cache servers.
-
-The following examples demonstrate the following:
-
-1.  A Java REST client creates a Person object on key 1. This client 
references the following supporting examples (also provided):
-1.  Geode cache client
-2.  REST client utility
-3.  Date Time utility
-4.  Person class
-5.  Gender class
-
-2.  A Ruby REST client also gets data for key 1 and updates it.
-3.  A Python REST Client demonstrates the creation and modification of objects.
-**Note:**
-An additional Python REST client reference application is available here: 
[https://github.com/gemfire/py-gemfire-rest](https://github.com/gemfire/py-gemfire-rest).
-
-The following Java examples assume a project directory structure similar to 
the following:
-
-
-## \#1. REST Java Client (RestClientApp.java)
-
-``` pre
-package org.apache.geode.restclient;
-
- import org.springframework.http.HttpHeaders;
- import org.springframework.http.MediaType;
- import org.springframework.http.HttpMethod;
- import org.springframework.http.HttpEntity;
- import org.springframework.http.ResponseEntity;
- import org.springframework.web.client.HttpClientErrorException;
- import org.springframework.web.client.HttpServerErrorException;
-
- import org.apache.geode.util.RestClientUtils;
-
- import java.util.ArrayList;
- import java.util.List;
-
-@SuppressWarnings( "unused")
- public class RestClientApp  {
-   private static final String PEOPLE_REGION =  "/People";
-
-   private static final String PERSON1_AS_JSON =  "{"
-  +  "\"@type\ ": \"org.apache.geode.domain.Person\ "," +  "\"id\ ": 
1,"
-   +  " \"firstName\ ": \"Jane\ "," +  " \"middleName\ ": \"H\ ","
-   +  " \"lastName\ ": \"Doe1\ "," +  " \"birthDate\ ": \"04/12/1983\ ","
-   +  "\"gender\ ": \"MALE\ "" + "}";
-
-   public static void main( final String... args)  throws Exception {
-doCreate(PEOPLE_REGION,  "1");
- System.out.println( "Programme has run successfully...!");
-  }
-
-   private static  HttpHeaders setAcceptAndContentTypeHeaders(){
-List acceptableMediaTypes =  new ArrayList();
-acceptableMediaTypes.add(MediaType.APPLICATION_JSON);
-
-HttpHeaders headers =  new HttpHeaders();
-headers.setAccept(acceptableMediaTypes);
-headers.setContentType(MediaType.APPLICATION_JSON);
- return headers;
-  }
-
-   private static void doCreate( final String regionNamePath,  final String 
key) {
-HttpHeaders headers =  setAcceptAndContentTypeHeaders();
-HttpEntity< String> entity =  new HttpEntity< String>(PERSON1_AS_JSON, 
headers);
- try {
-  ResponseEntity< String> result = 
RestClientUtils.getRestTemplate().exchange(
- "http://localhost:8080/gemfire-api/v1/People?key=1; , 
HttpMethod.POST,
-entity,  String.class);
-
-   System.out.println( "STATUS_CODE = " + result.getStatusCode().value());
-   System.out.println( "HAS_BODY = " + result.hasBody());
-   System.out.println( "LOCATION_HEADER = " + 
result.getHeaders().getLocation().toString());
-}  catch (HttpClientErrorException e) {
-   System.out.println( "Http Client encountered error, msg:: " + 
e.getMessage());
-}  catch(HttpServerErrorException se) {
-   System.out.println( "Server encountered error, msg::" + 
se.getMessage());
-}  catch (Exception e) {
-   System.out.println( "Unexpected ERROR...!!");
-}
-  }
-}
-```
-
-## \#1a. Geode Cache Java Client (MyJavaClient.java)
-
-``` pre
-package org.apache.geode.javaclient;
-
- import java.util.Calendar;
- import java.util.HashMap;
- import java.util.Map;
-
- import org.apache.geode.cache.Region;
- import org.apache.geode.cache.client.ClientCache;
- import org.apache.geode.cache.client.ClientCacheFactory;
- import org.apache.geode.cache.client.ClientRegionFactory;
- import org.apache.geode.cache.client.ClientRegionShortcut;
- import org.apache.geode.domain.Gender;
- import org.apache.geode.domain.Person;
- import org.apache.geode.pdx.PdxInstance;
- import org.apache.geode.util.DateTimeUtils;
-
- public class MyJavaClient {
-
-   public static void main( String[] args) {
-ClientCacheFactory 

[01/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEODE-1964 [created] ff80a9315


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
deleted file mode 100644
index a7e1e16..000
--- a/geode-docs/tools_modules/gfsh/command-pages/export.html.md.erb
+++ /dev/null
@@ -1,254 +0,0 @@

-title: export

-
-
-
-Export configurations, data, logs and stack-traces.
-
--   **[export 
cluster-configuration](../../../tools_modules/gfsh/command-pages/export.html#topic_mdv_jgz_ck)**
-
-Exports a cluster configuration zip file that contains the `cache.xml` 
files, `gemfire.properties` files, and application jar files needed to 
configure and operate a Geode distributed system.
-
--   **[export 
config](../../../tools_modules/gfsh/command-pages/export.html#topic_C7C69306F93743459E65D46537F4A1EE)**
-
-Export configuration properties for a member or members.
-
--   **[export 
data](../../../tools_modules/gfsh/command-pages/export.html#topic_263B70069BFC4A7185F86B3272011734)**
-
-Export user data from a region to a file.
-
--   **[export 
logs](../../../tools_modules/gfsh/command-pages/export.html#topic_B80978CC659244AE91E2B8CE56EBDFE3)**
-
-Export logs to a given directory.
-
--   **[export 
offline-disk-store](../../../tools_modules/gfsh/command-pages/export.html#topic_sjg_bvt_gq)**
-
-Export region data from an offline disk store into gemfire snapshot files.
-
--   **[export 
stack-traces](../../../tools_modules/gfsh/command-pages/export.html#topic_195D27B8B2B64A4E84CF2256636D54BD)**
-
-Export the stack trace for a member or members.
-
-## export 
cluster-configuration
-
-Exports a cluster configuration zip file that contains the `cache.xml` files, 
`gemfire.properties` files, and application jar files needed to configure and 
operate a Geode distributed system.
-
-**Availability:** Online. You must be connected in `gfsh` to a JMX Manager 
member to use this command.
-
-See [Overview of the Cluster Configuration 
Service](../../../configuring/cluster_config/gfsh_persist.html#concept_r22_hyw_bl).
-
-**Syntax:**
-
-``` pre
-export cluster-configuration --zip-file-name=value [--dir=value]
-```
-
-
-
-| Name  | Description  
| Default Value 
|
-|---|--|---|
-| \\-\\-zip-file-name | *Required.* File 
name of the zip file to contain the exported cluster configuration. |  
 |
-| \\-\\-dir   | Directory where 
the cluster configuration zip files is saved.| Locator 
directory |
-
-Table 1. Export Cluster-Configuration Parameters
-
-**Example Commands:**
-
-``` pre
-gfsh>export cluster-configuration 
--zip-file-name=/home/username/gemfire80/myClusterConfig.zip
-```
-
-**Sample Output:**
-
-``` pre
-gfsh>export cluster-configuration --zip-file-name=mySharedConfig.zip
-Downloading cluster configuration : 
/home/username/gemfire80/myClusterConfig.zip
-```
-
-## export config
-
-Export configuration properties for a member or members.
-
-If you do not specify any parameters, all member configuration will be 
exported.
-
-**Availability:** Online. You must be connected in `gfsh` to a JMX Manager 
member to use this command.
-
-**Syntax:**
-
-``` pre
-export config [--member=value(,value)*] [--group=value(,value)*]
-[--dir=value]
-```
-
-
-
-| Name   | Description 
 |
-||--|
-| \\-\\-member | Name/Id of the 
member(s) whose configuration will be exported.   |
-| \\-\\-group  | Group(s) of members 
whose configuration will be exported.|
-| \\-\\-dir| Directory to which the 
exported configuration files will be written. |
-
-Table 2. Export Config Parameters
-
-**Example Commands:**
-
-``` pre
-export config
-export config --member=member1
-```
-
-**Sample Output:**
-
-``` pre
-gfsh>export config --member=member1
-Downloading Cache XML file: c:\PivotalGemFire70\Latest\.\member1-cache.xml
-Downloading properties file: c:\PivotalGemFire70\Latest\.\member1-gf.properties
-```
-
-## export data
-
-Export user data from a region to a file.
-
-**Availability:** Online. You must be connected in `gfsh` to a JMX Manager 
member to use this command.
-
-**Syntax:**
-
-``` pre
-export data --region=value --file=value --member=value
-```
-
-
-
-| Name

[03/51] [partial] incubator-geode git commit: GEODE-1964: native client documentation (note: contains references to images in the geode-docs directories)

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ff80a931/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
--
diff --git a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb 
b/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
deleted file mode 100644
index 1bbb070..000
--- a/geode-docs/tools_modules/gfsh/command-pages/alter.html.md.erb
+++ /dev/null
@@ -1,503 +0,0 @@

-title: alter

-
-
-
-Modify an existing Geode resource.
-
--   **[alter 
disk-store](../../../tools_modules/gfsh/command-pages/alter.html#topic_99BCAD98BDB5470189662D2F308B68EB)**
-
-Modify or remove a region from an offline disk-store.
-
--   **[alter 
region](../../../tools_modules/gfsh/command-pages/alter.html#topic_E74ED23CB60342538B2175C326E7D758)**
-
-Alters the configuration of a region.
-
--   **[alter 
runtime](../../../tools_modules/gfsh/command-pages/alter.html#topic_7E6B7E1B972D4F418CB45354D1089C2B)**
-
-Alters configuration properties for all members or a subset of members 
while the member or members are running.
-
-## alter disk-store
-
-Modify or remove a region from an offline disk-store.
-
-When modifying a region's configuration, it is customary to take the region 
off-line and restart using the new configuration. You can use the `alter
 disk-store` command to change the configuration of the region 
stored in the disk-store to match the configuration you will use at restart.
-
-**Availability:** Offline.
-
-**Syntax:**
-
-``` pre
-alter disk-store --name=value --region=value --disk-dirs=value(,value)*
-[--compressor(=value)] [--concurrency-level=value]
-[--enable-statistics=value] [--initial-capacity=value] 
[--load-factor=value]
-[--lru-algorithm=value] [--lru-action=value] [--lru-limit=value]
-[--off-heap(=value)] [--remove(=value)]
-```
-
-The three required options, `--name`, `--region`, and `--disk-dirs`, identify 
the disk store and region to be altered. If no additional options are 
specified, `gfsh` displays the current configuration without making any changes.
-
-
-
-
-
-
-
-
-Name
-Description
-
-
-
-
-\-\-name
-Required. Name of the disk-store whose contents will be 
altered.
-
-
-\-\-region
-Required. Name (including path) of the region using the disk 
store.
-
-
-\-\-disk-dirs
-Required. Directories where the data for the disk store was 
previously written.
-
-
-\-\-compressor
-The fully-qualified class name of the compressor to use when compressing 
region entry values. A value of none removes the 
compressor.
-
-
-\-\-concurrency-level
-An estimate of the maximum number of application threads that will 
concurrently access a region entry. Together with \-\-initial-capacity and \-\-load-factor, sets the parameters on the underlying java.util.ConcurrentHashMap used for storing region 
entries. This attribute does not apply to partitioned regions.
-
-
-\-\-enable-statistics
-Enables statistics for the region. Valid values are true or false. If the 
parameter is specified without a value, the value of true is used.
-
-
-\-\-initial-capacity
-Together with \-\-concurrency-level 
and \-\-load-factor, sets the parameters 
on the underlying java.util.ConcurrentHashMap 
used for storing region entries.
-
-
-\-\-load-factor
-Together with \-\-concurrency-level 
and \-\-initial-capacity, sets the 
parameters on the underlying java.util.ConcurrentHashMap used for storing region entries. 
This must be a floating point number between 0 and 1, inclusive.
-
-
-\-\-lru-action
-Action to take when evicting entries from the region. Valid values are:
-
-none
-overflow-to-disk
-local-destroy
-
-
-
-\-\-lru-algorithm
-Least recently used eviction algorithm. Valid types are:
-
-none
-lru-entry-count
-lru-heap-percentage
-lru-memory-size
-
-
-
-\-\-lru-limit
-Number of entries allowed in the region before eviction occurs.
-
-
-\-\-off-heap
-Specifies whether the region values are in heap memory or off-heap memory. 
When true, region values are in off-heap memory. If the parameter is specified 
without a value, the value of true is used.
-
-
-\-\-remove
-Specifies whether to remove the region from the disk-store. If the 
parameter is specified without a value, the value of true is used. Note: \-\-remove deletes all persistent data for the 
region. Consider copying the disk store files to a backup before using this 
option if you might want to retrieve the data at a later date.
-
-
-
-
-**Example Commands:**
-
-``` pre
-alter disk-store --name=DiskStore1 --region=region1 
--disk-dirs=/Disks/DiskStore1 --off-heap
-alter disk-store --name=DiskStore1 --region=region1 
--disk-dirs=/Disks/DiskStore1 --remove
-```
-
-## alter region
-
-Alters the configuration of a region.
-
-**Availability:** Online. You must be connected in gfsh to a JMX Manager member to use this command.
-
-**Syntax:**
-
-``` pre
-alter region --name=value [--group=value(,value)*]
-

[1/2] incubator-geode git commit: GEODE-1364: Resolved as a part of GEODE-1588

[nnag]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop f82626f46 -> 18c2dc3fb


GEODE-1364: Resolved as a part of GEODE-1588


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

Branch: refs/heads/develop
Commit: 0b61ae69d8486c137a30160c22d8985c37f76324
Parents: f82626f
Author: nabarun 
Authored: Tue Oct 4 15:33:13 2016 -0700
Committer: nabarun 
Committed: Tue Oct 4 15:33:13 2016 -0700

--
 .../internal/cache/wan/serial/SerialWANPropagationDUnitTest.java| 1 -
 1 file changed, 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/0b61ae69/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
--
diff --git 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
index a3c5ee4..2b97d7a 100644
--- 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
+++ 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
@@ -968,7 +968,6 @@ public class SerialWANPropagationDUnitTest extends 
WANTestBase {
 vm3.invoke(() -> WANTestBase.validateRegionSize(getTestMethodName() + 
"_RR_1", 8000));
   }
 
-  @Category(FlakyTest.class) // GEODE-1364, 1478
   @Test
   public void testReplicatedSerialPropagationToTwoWanSites() throws Exception {
 Integer lnPort = createFirstLocatorWithDSId(1);

incubator-geode git commit: GEODE-1804: Refactored the test

[nnag]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop f0dab0aa3 -> f82626f46


GEODE-1804: Refactored the test

* Refactored the test to have the correct order of creation of cache, 
region and sender-receivers.
* Additional validity check for the local region size.


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

Branch: refs/heads/develop
Commit: f82626f46babe0f5fcce8dafd5deab2ca6b86860
Parents: f0dab0a
Author: nabarun 
Authored: Tue Oct 4 15:26:45 2016 -0700
Committer: nabarun 
Committed: Tue Oct 4 15:26:45 2016 -0700

--
 .../serial/SerialWANPropagationDUnitTest.java   | 55 +++-
 1 file changed, 29 insertions(+), 26 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/f82626f4/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
--
diff --git 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
index 52cd25f..a3c5ee4 100644
--- 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
+++ 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/serial/SerialWANPropagationDUnitTest.java
@@ -527,7 +527,6 @@ public class SerialWANPropagationDUnitTest extends 
WANTestBase {
 getTestMethodName() + "_RR_1", 1000 ));
   }
 
-  @Category(FlakyTest.class) // GEODE-1804
   @Test
   public void testReplicatedSerialPropagationWithRemoteRegionDestroy3()
   throws Exception {
@@ -535,51 +534,52 @@ public class SerialWANPropagationDUnitTest extends 
WANTestBase {
 Integer nyPort = (Integer)vm1.invoke(() -> 
WANTestBase.createFirstRemoteLocator( 2, lnPort ));
 // these are part of remote site
 createCacheInVMs(nyPort, vm2, vm3);
-createReceiverInVMs(vm2, vm3);
-
-// these are part of local site
-createCacheInVMs(lnPort, vm4, vm5, vm6, vm7);
-
-// senders are created on local site
-vm4.invoke(() -> WANTestBase.createSender( "ln", 2,
-false, 100, 200, false, false, null, true ));
-vm5.invoke(() -> WANTestBase.createSender( "ln", 2,
-false, 100, 200, false, false, null, true ));
 
 // create one RR (RR_1) on remote site
 vm2.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", null, isOffHeap()  ));
+  getTestMethodName() + "_RR_1", null, isOffHeap()  ));
 vm3.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", null, isOffHeap()  ));
+  getTestMethodName() + "_RR_1", null, isOffHeap()  ));
 
 // create another RR (RR_2) on remote site
 vm2.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_2", null, isOffHeap()  ));
+  getTestMethodName() + "_RR_2", null, isOffHeap()  ));
 vm3.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_2", null, isOffHeap()  ));
-
-// start the senders on local site
-startSenderInVMs("ln", vm4, vm5);
+  getTestMethodName() + "_RR_2", null, isOffHeap()  ));
+
+createReceiverInVMs(vm2, vm3);
+
+// these are part of local site
+createCacheInVMs(lnPort, vm4, vm5, vm6, vm7);
 
 // create one RR (RR_1) on local site
 vm4.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
+  getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
 vm5.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
+  getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
 vm6.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
+  getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
 vm7.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
+  getTestMethodName() + "_RR_1", "ln", isOffHeap()  ));
 
 // create another RR (RR_2) on local site
 vm4.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_2", "ln", isOffHeap()  ));
+  getTestMethodName() + "_RR_2", "ln", isOffHeap()  ));
 vm5.invoke(() -> WANTestBase.createReplicatedRegion(
-getTestMethodName() + "_RR_2", "ln", isOffHeap()  ));
+  getTestMethodName() + "_RR_2", "ln", isOffHeap() 

[2/3] incubator-geode git commit: GEODE-1570 - developer REST API should be secured

[jinmeiliao]

GEODE-1570 - developer REST API should be secured

* Merged with develop after org.apache package rename
* Moved classes to internal.
* this closes #251


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

Branch: refs/heads/release/1.0.0-incubating
Commit: 7b21520b746413913b5ad5ed640e5c883eeccaab
Parents: d76eee4
Author: Kevin Duling 
Authored: Wed Sep 21 08:50:46 2016 -0700
Committer: Jinmei Liao 
Committed: Mon Oct 3 13:26:44 2016 -0700

--
 .../internal/web/RestSecurityDUnitTest.java | 247 +--
 .../web/RestSecurityEndpointsDUnitTest.java | 422 +++
 .../src/main/webapp/WEB-INF/spring-security.xml |   2 +-
 geode-web-api/build.gradle  |   6 +-
 .../web/controllers/AbstractBaseController.java |  54 ++-
 .../web/controllers/BaseControllerAdvice.java   |  78 +++-
 .../web/controllers/CommonCrudController.java   |  87 ++--
 .../controllers/FunctionAccessController.java   |  36 +-
 .../web/controllers/PdxBasedCrudController.java |  44 +-
 .../web/controllers/QueryAccessController.java  | 108 ++---
 .../web/security/GeodeAuthentication.java   |  37 ++
 .../security/GeodeAuthenticationProvider.java   |  56 +++
 .../internal/web/security/GeodeAuthority.java   |  47 +++
 .../web/security/RestSecurityConfiguration.java |  76 
 .../src/main/webapp/WEB-INF/geode-servlet.xml   |  11 +-
 geode-web-api/src/main/webapp/WEB-INF/web.xml   |  20 +-
 gradle/dependency-versions.properties   |   4 +-
 17 files changed, 1116 insertions(+), 219 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/7b21520b/geode-assembly/src/test/java/org/apache/geode/rest/internal/web/RestSecurityDUnitTest.java
--
diff --git 
a/geode-assembly/src/test/java/org/apache/geode/rest/internal/web/RestSecurityDUnitTest.java
 
b/geode-assembly/src/test/java/org/apache/geode/rest/internal/web/RestSecurityDUnitTest.java
index df146a6..a9d90ed 100644
--- 
a/geode-assembly/src/test/java/org/apache/geode/rest/internal/web/RestSecurityDUnitTest.java
+++ 
b/geode-assembly/src/test/java/org/apache/geode/rest/internal/web/RestSecurityDUnitTest.java
@@ -22,75 +22,236 @@ import java.io.BufferedReader;
 import java.io.IOException;
 import java.io.InputStream;
 import java.io.InputStreamReader;
+import java.net.MalformedURLException;
+import java.net.URL;
+import java.nio.charset.StandardCharsets;
 
+import org.apache.geode.internal.AvailablePortHelper;
+import org.apache.geode.security.AbstractSecureServerDUnitTest;
+import org.apache.geode.test.junit.categories.DistributedTest;
+import org.apache.geode.test.junit.categories.SecurityTest;
 import org.apache.http.HttpEntity;
+import org.apache.http.HttpHost;
+import org.apache.http.HttpResponse;
+import org.apache.http.auth.AuthScope;
+import org.apache.http.auth.UsernamePasswordCredentials;
+import org.apache.http.client.AuthCache;
 import org.apache.http.client.ClientProtocolException;
-import org.apache.http.client.methods.CloseableHttpResponse;
+import org.apache.http.client.CredentialsProvider;
+import org.apache.http.client.methods.HttpDelete;
 import org.apache.http.client.methods.HttpGet;
+import org.apache.http.client.methods.HttpHead;
+import org.apache.http.client.methods.HttpPost;
+import org.apache.http.client.methods.HttpPut;
+import org.apache.http.client.protocol.HttpClientContext;
+import org.apache.http.entity.StringEntity;
+import org.apache.http.impl.auth.BasicScheme;
+import org.apache.http.impl.client.BasicAuthCache;
+import org.apache.http.impl.client.BasicCredentialsProvider;
 import org.apache.http.impl.client.CloseableHttpClient;
 import org.apache.http.impl.client.HttpClients;
-import org.json.JSONArray;
-import org.json.JSONException;
-import org.junit.Test;
+import org.json.JSONTokener;
 import org.junit.experimental.categories.Category;
 
-import org.apache.geode.internal.AvailablePortHelper;
-import org.apache.geode.security.AbstractSecureServerDUnitTest;
-import org.apache.geode.test.junit.categories.DistributedTest;
-import org.apache.geode.test.junit.categories.SecurityTest;
 
-@Category({ DistributedTest.class, SecurityTest.class})
+@Category({ DistributedTest.class, SecurityTest.class })
 public class RestSecurityDUnitTest extends AbstractSecureServerDUnitTest {
-  private String endPoint = null;
-  public RestSecurityDUnitTest(){
+
+  public final static String PROTOCOL = "http";
+  public final static String HOSTNAME = "localhost";
+  public final static String CONTEXT = "/geode/v1";
+
+  private final 

[1/3] incubator-geode git commit: GEODE-1570 - developer REST API should be secured

[jinmeiliao]

Repository: incubator-geode
Updated Branches:
  refs/heads/release/1.0.0-incubating d76eee424 -> 864fc08fa


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/7b21520b/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthentication.java
--
diff --git 
a/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthentication.java
 
b/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthentication.java
new file mode 100644
index 000..c4226f6
--- /dev/null
+++ 
b/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthentication.java
@@ -0,0 +1,37 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.geode.rest.internal.web.security;
+
+import 
org.springframework.security.authentication.UsernamePasswordAuthenticationToken;
+import org.springframework.security.core.authority.AuthorityUtils;
+
+class GeodeAuthentication extends UsernamePasswordAuthenticationToken {
+  /**
+   * This constructor should only be used by 
AuthenticationManager or AuthenticationProvider
+   * implementations that are satisfied with producing a trusted (i.e. {@link 
#isAuthenticated()} = true)
+   * authentication token.
+   * @param principal
+   * @param credentials
+   */
+  public GeodeAuthentication(final Object principal,
+ final Object credentials) {
+super(principal, credentials, AuthorityUtils.NO_AUTHORITIES);
+  }
+
+}

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/7b21520b/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthenticationProvider.java
--
diff --git 
a/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthenticationProvider.java
 
b/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthenticationProvider.java
new file mode 100644
index 000..c482047
--- /dev/null
+++ 
b/geode-web-api/src/main/java/org/apache/geode/rest/internal/web/security/GeodeAuthenticationProvider.java
@@ -0,0 +1,56 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ *
+ */
+
+package org.apache.geode.rest.internal.web.security;
+
+import org.apache.shiro.subject.Subject;
+import org.springframework.security.authentication.AuthenticationProvider;
+import org.springframework.security.authentication.BadCredentialsException;
+import 
org.springframework.security.authentication.UsernamePasswordAuthenticationToken;
+import org.springframework.security.core.Authentication;
+import org.springframework.security.core.AuthenticationException;
+import org.springframework.stereotype.Component;
+
+import org.apache.geode.internal.security.IntegratedSecurityService;
+import org.apache.geode.security.AuthenticationFailedException;
+
+
+@Component
+public class GeodeAuthenticationProvider implements AuthenticationProvider {
+
+  @Override
+  public Authentication authenticate(Authentication authentication) throws 
AuthenticationException {
+String username = authentication.getName();
+String password = authentication.getCredentials().toString();
+
+try {
+  Subject subject = 
IntegratedSecurityService.getSecurityService().login(username, password);
+  if (subject != null) {
+return new 

[3/3] incubator-geode git commit: GEODE-1570: make GemFireVersion.properties available in the geode-core test source so that other projects that depends on the geode-core-test can access it.

[jinmeiliao]

GEODE-1570: make GemFireVersion.properties available in the geode-core test 
source so that other projects that depends on the geode-core-test can access it.


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

Branch: refs/heads/release/1.0.0-incubating
Commit: 864fc08fa6ad44c054fb8e9d27fd90dd777ce598
Parents: 7b21520
Author: Jinmei Liao 
Authored: Tue Oct 4 15:10:42 2016 -0700
Committer: Jinmei Liao 
Committed: Tue Oct 4 15:10:42 2016 -0700

--
 geode-core/build.gradle | 3 +++
 1 file changed, 3 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/864fc08f/geode-core/build.gradle
--
diff --git a/geode-core/build.gradle b/geode-core/build.gradle
index b2e5a4e..3cbdfbe 100755
--- a/geode-core/build.gradle
+++ b/geode-core/build.gradle
@@ -131,6 +131,9 @@ sourceSets {
   main {
 output.dir(generatedResources, builtBy: 'createVersionPropertiesFile')
   }
+  test {
+output.dir(generatedResources, builtBy: 'createVersionPropertiesFile')
+  }
 }
 
 // Creates the version properties file and writes it to the classes dir

incubator-geode git commit: GEODE-1384: Stat issues were fixed as a part of other tickets.

[nnag]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop 71627eb81 -> 15a5267c4


GEODE-1384: Stat issues were fixed as a part of other tickets.

* Code refactored to have the correct order of creation of cache, 
region and sender receivers.


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

Branch: refs/heads/develop
Commit: 15a5267c47852efbed14cb9b85614a1208145c33
Parents: 71627eb
Author: nabarun 
Authored: Tue Oct 4 15:11:30 2016 -0700
Committer: nabarun 
Committed: Tue Oct 4 15:13:37 2016 -0700

--
 .../wan/parallel/ParallelWANStatsDUnitTest.java | 27 ++--
 1 file changed, 19 insertions(+), 8 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/15a5267c/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/parallel/ParallelWANStatsDUnitTest.java
--
diff --git 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/parallel/ParallelWANStatsDUnitTest.java
 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/parallel/ParallelWANStatsDUnitTest.java
index 4a68608..9d2f1a5 100644
--- 
a/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/parallel/ParallelWANStatsDUnitTest.java
+++ 
b/geode-wan/src/test/java/org/apache/geode/internal/cache/wan/parallel/ParallelWANStatsDUnitTest.java
@@ -16,6 +16,7 @@
  */
 package org.apache.geode.internal.cache.wan.parallel;
 
+import com.jayway.awaitility.Awaitility;
 import org.junit.Ignore;
 import org.junit.experimental.categories.Category;
 import org.junit.Test;
@@ -32,6 +33,7 @@ import static org.apache.geode.test.dunit.IgnoredException.*;
 import java.util.ArrayList;
 import java.util.HashMap;
 import java.util.Map;
+import java.util.concurrent.TimeUnit;
 
 import org.junit.experimental.categories.Category;
 
@@ -224,31 +226,40 @@ public class ParallelWANStatsDUnitTest extends 
WANTestBase{
 vm3.invoke(() -> WANTestBase.checkGatewayReceiverStats(10, NUM_PUTS, 
NUM_PUTS ));
   }
   
-  @Category(FlakyTest.class) // GEODE-1384
   @Test
   public void testParallelPropagationHA() throws Exception {
 Integer lnPort = (Integer)vm0.invoke(() -> 
WANTestBase.createFirstLocatorWithDSId( 1 ));
 Integer nyPort = (Integer)vm1.invoke(() -> 
WANTestBase.createFirstRemoteLocator( 2, lnPort ));
 
 createCacheInVMs(nyPort, vm2);
-createReceiverInVMs(vm2);
 
-createSenders(lnPort);
-
 createReceiverPR(vm2, 0);
-
+
+createReceiverInVMs(vm2);
+
+createCacheInVMs(lnPort, vm4, vm5, vm6, vm7);
+
 createSenderPRs(3);
 
+vm4.invoke(() -> WANTestBase.createSender( "ln", 2,
+  true, 100, 10, true, false, null, true ));
+vm5.invoke(() -> WANTestBase.createSender( "ln", 2,
+  true, 100, 10, true, false, null, true ));
+vm6.invoke(() -> WANTestBase.createSender( "ln", 2,
+  true, 100, 10, true, false, null, true ));
+vm7.invoke(() -> WANTestBase.createSender( "ln", 2,
+  true, 100, 10, true, false, null, true ));
+
 startSenderInVMs("ln", vm4, vm5, vm6, vm7);
 
 AsyncInvocation inv1 = vm5.invokeAsync(() -> WANTestBase.doPuts( testName, 
1000 ));
-pause(200);
+vm2.invoke(() -> Awaitility.await().atMost(3, 
TimeUnit.MILLISECONDS).until(() ->
+  assertEquals("Waiting for first batch to be 
received",true,getRegionSize(testName) > 10)));
 AsyncInvocation inv2 = vm4.invokeAsync(() -> WANTestBase.killSender());
 inv1.join();
 inv2.join();
 
-vm2.invoke(() -> WANTestBase.validateRegionSize(
-testName, 1000 ));
+vm2.invoke(() -> WANTestBase.validateRegionSize(testName, 1000 ));
 
 ArrayList v5List = (ArrayList)vm5.invoke(() -> 
WANTestBase.getSenderStats( "ln", 0));
 ArrayList v6List = (ArrayList)vm6.invoke(() -> 
WANTestBase.getSenderStats( "ln", 0));

incubator-geode git commit: GEODE-1963 Fix a pathname typo in the website README.md revealed during the recent lucene.xsd addition.

[dbarnes]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop 118c0d467 -> 71627eb81


GEODE-1963 Fix a pathname typo in the website README.md revealed during the 
recent lucene.xsd addition.


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

Branch: refs/heads/develop
Commit: 71627eb8154477c742eb045732967826b2fc1b47
Parents: 118c0d4
Author: Dave Barnes 
Authored: Tue Oct 4 15:10:16 2016 -0700
Committer: Dave Barnes 
Committed: Tue Oct 4 15:10:16 2016 -0700

--
 geode-site/website/README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/71627eb8/geode-site/website/README.md
--
diff --git a/geode-site/website/README.md b/geode-site/website/README.md
index 474e6ca..ff9ee89 100644
--- a/geode-site/website/README.md
+++ b/geode-site/website/README.md
@@ -77,7 +77,7 @@ Here is one way to accomplish this:
 
 1. On the __develop__ branch
 
-$ cd geode-site-website
+$ cd geode-site/website
 $ nanoc compile
 $ cd ../content
 $ tar cvf new-website-content.tar .

incubator-geode git commit: GEODE-1963: Add lucene xsd to web site

[jasonhuynh]

Repository: incubator-geode
Updated Branches:
  refs/heads/asf-site 8ed53ee29 -> 9aebc117d


GEODE-1963: Add lucene xsd to web site


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

Branch: refs/heads/asf-site
Commit: 9aebc117deac97d84a2a35b6aff029c1d01d1fc1
Parents: 8ed53ee
Author: Jason Huynh 
Authored: Tue Oct 4 15:07:15 2016 -0700
Committer: Jason Huynh 
Committed: Tue Oct 4 15:07:15 2016 -0700

--
 schema/cache/lucene-1.0.xsd | 58 
 1 file changed, 58 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/9aebc117/schema/cache/lucene-1.0.xsd
--
diff --git a/schema/cache/lucene-1.0.xsd b/schema/cache/lucene-1.0.xsd
new file mode 100644
index 000..ec82c2f
--- /dev/null
+++ b/schema/cache/lucene-1.0.xsd
@@ -0,0 +1,58 @@
+
+
+http://geode.apache.org/schema/lucene;
+xmlns:xsd="http://www.w3.org/2001/XMLSchema;
+elementFormDefault="qualified"
+attributeFormDefault="unqualified"
+version="1.0">
+  
+  http://geode.apache.org/schema/cache;
+  schemaLocation="http://geode.apache.org/schema/cache/cache-1.0.xsd"/>
+  
+  
+
+  
+  
+
+   
+ 
+   
+   
+   
+   
+ 
+   
+   
+
+  
+

[incubator-geode] Git Push Summary

[klund]

Repository: incubator-geode
Updated Branches:
  refs/heads/feature/GEODE-1930 [created] 1feea53c2

incubator-geode git commit: GEODE-1902: add apache license header

[klund]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop 1feea53c2 -> 118c0d467


GEODE-1902: add apache license header


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

Branch: refs/heads/develop
Commit: 118c0d467e0ad80d98ff2aaa1a3d22d26b40696f
Parents: 1feea53
Author: Kirk Lund 
Authored: Tue Oct 4 14:38:10 2016 -0700
Committer: Kirk Lund 
Committed: Tue Oct 4 14:38:10 2016 -0700

--
 .../geode/internal/logging/log4j/Configuration.java | 16 
 1 file changed, 16 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/118c0d46/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
--
diff --git 
a/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
 
b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
index 8f7ca1a..d55b768 100644
--- 
a/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
+++ 
b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
@@ -1,3 +1,19 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
 package org.apache.geode.internal.logging.log4j;
 
 import static org.assertj.core.api.Assertions.assertThat;

incubator-geode git commit: GEODE-1963: Add lucene xsd to website content

[jasonhuynh]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop 375c6c5bc -> 1feea53c2


GEODE-1963: Add lucene xsd to website content


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

Branch: refs/heads/develop
Commit: 1feea53c2032bc79df39a653945e53d24f9c9291
Parents: 375c6c5
Author: Jason Huynh 
Authored: Tue Oct 4 09:31:14 2016 -0700
Committer: Jason Huynh 
Committed: Tue Oct 4 14:04:04 2016 -0700

--
 .../website/content/schema/cache/lucene-1.0.xsd | 58 
 1 file changed, 58 insertions(+)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/1feea53c/geode-site/website/content/schema/cache/lucene-1.0.xsd
--
diff --git a/geode-site/website/content/schema/cache/lucene-1.0.xsd 
b/geode-site/website/content/schema/cache/lucene-1.0.xsd
new file mode 100644
index 000..ec82c2f
--- /dev/null
+++ b/geode-site/website/content/schema/cache/lucene-1.0.xsd
@@ -0,0 +1,58 @@
+
+
+http://geode.apache.org/schema/lucene;
+xmlns:xsd="http://www.w3.org/2001/XMLSchema;
+elementFormDefault="qualified"
+attributeFormDefault="unqualified"
+version="1.0">
+  
+  http://geode.apache.org/schema/cache;
+  schemaLocation="http://geode.apache.org/schema/cache/cache-1.0.xsd"/>
+  
+  
+
+  
+  
+
+   
+ 
+   
+   
+   
+   
+ 
+   
+   
+
+  
+

[2/3] incubator-geode git commit: GEODE-1902 - Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for backwards compatibility

[klund]

GEODE-1902 - Add GEMFIRE_VERBOSE LogMarker as alias of GEODE_VERBOSE for 
backwards compatibility

This closes #247


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

Branch: refs/heads/develop
Commit: c80cba2c81f55736121a0d12d7e01b3249c20bdd
Parents: 8929e93
Author: Kevin Duling 
Authored: Mon Sep 26 16:10:34 2016 -0700
Committer: Kirk Lund 
Committed: Tue Oct 4 13:14:19 2016 -0700

--
 .../geode/internal/logging/LogService.java  | 154 ++-
 .../internal/logging/log4j/Configurator.java|  69 -
 .../geode/internal/logging/log4j/LogMarker.java |  78 ++
 .../logging/log4j/LogMarkerJUnitTest.java   | 112 ++
 .../logging/log4j/custom/log4j2-custom.xml  |  52 ---
 5 files changed, 294 insertions(+), 171 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/c80cba2c/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
--
diff --git 
a/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java 
b/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
index 2c6eda3..405434d 100644
--- a/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
+++ b/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
@@ -30,6 +30,7 @@ import org.apache.logging.log4j.core.config.LoggerConfig;
 import org.apache.logging.log4j.core.lookup.StrLookup;
 import org.apache.logging.log4j.core.lookup.StrSubstitutor;
 import org.apache.logging.log4j.status.StatusLogger;
+
 import org.apache.geode.internal.logging.log4j.AppenderContext;
 import org.apache.geode.internal.logging.log4j.ConfigLocator;
 import org.apache.geode.internal.logging.log4j.Configurator;
@@ -42,75 +43,82 @@ import 
org.apache.geode.internal.logging.log4j.message.GemFireParameterizedMessa
  */
 @SuppressWarnings("unused")
 public class LogService extends LogManager {
+
   // This is highest point in the hierarchy for all Geode logging
   public static final String ROOT_LOGGER_NAME = "";
   public static final String BASE_LOGGER_NAME = "org.apache.geode";
   public static final String MAIN_LOGGER_NAME = "org.apache.geode";
   public static final String SECURITY_LOGGER_NAME = 
"org.apache.geode.security";
-  
-  public static final String GEMFIRE_VERBOSE_FILTER = "{GEODE_VERBOSE}";
-  
-  protected static final String STDOUT = "STDOUT";
 
-  private static final PropertyChangeListener propertyChangeListener = new 
PropertyChangeListenerImpl();
-  
+  public static final String GEODE_VERBOSE_FILTER = "{GEODE_VERBOSE}";
+  public static final String GEMFIRE_VERBOSE_FILTER = "{GEMFIRE_VERBOSE}";
   public static final String DEFAULT_CONFIG = "/log4j2.xml";
   public static final String CLI_CONFIG = "/log4j2-cli.xml";
-
+  protected static final String STDOUT = "STDOUT";
+  private static final PropertyChangeListener propertyChangeListener = new 
PropertyChangeListenerImpl();
   /**
* Name of variable that is set to "true" in log4j2.xml to indicate that it 
is the default geode config xml.
*/
   private static final String GEMFIRE_DEFAULT_PROPERTY = "geode-default";
-  
-  /** Protected by static synchronization. Used for removal and adding stdout 
back in. */
+
+  /**
+   * Protected by static synchronization. Used for removal and adding stdout 
back in.
+   */
   private static Appender stdoutAppender;
-  
+
   static {
 init();
   }
+
+  private LogService() {
+// do not instantiate
+  }
+
   private static void init() {
-LoggerContext context = ((org.apache.logging.log4j.core.Logger) 
LogManager.getLogger(BASE_LOGGER_NAME, 
GemFireParameterizedMessageFactory.INSTANCE)).getContext();
+LoggerContext context = ((org.apache.logging.log4j.core.Logger) 
LogManager.getLogger(BASE_LOGGER_NAME, 
GemFireParameterizedMessageFactory.INSTANCE))
+  .getContext();
 context.removePropertyChangeListener(propertyChangeListener);
 context.addPropertyChangeListener(propertyChangeListener);
 context.reconfigure(); // propertyChangeListener invokes 
configureFastLoggerDelegating
 configureLoggers(false, false);
   }
-  
+
   public static void initialize() {
 new LogService();
   }
-  
+
   public static void reconfigure() {
 init();
   }
-  
+
   public static void configureLoggers(final boolean hasLogFile, final boolean 
hasSecurityLogFile) {
 Configurator.getOrCreateLoggerConfig(BASE_LOGGER_NAME, true, false);
 Configurator.getOrCreateLoggerConfig(MAIN_LOGGER_NAME, 

[1/3] incubator-geode git commit: GEODE-1902: reformat code

[klund]

Repository: incubator-geode
Updated Branches:
  refs/heads/develop 8929e93bd -> 375c6c5bc


GEODE-1902: reformat code


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

Branch: refs/heads/develop
Commit: 8703f2a71526a35f8945698611d18a0b8b9bd373
Parents: c80cba2
Author: Kirk Lund 
Authored: Tue Oct 4 11:45:46 2016 -0700
Committer: Kirk Lund 
Committed: Tue Oct 4 13:14:19 2016 -0700

--
 .../geode/internal/logging/LogService.java  | 35 +++
 .../internal/logging/log4j/Configurator.java| 20 ++---
 .../geode/internal/logging/log4j/LogMarker.java | 45 
 .../logging/log4j/LogMarkerJUnitTest.java   |  6 +--
 4 files changed, 40 insertions(+), 66 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/8703f2a7/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
--
diff --git 
a/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java 
b/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
index 405434d..baf01e1 100644
--- a/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
+++ b/geode-core/src/main/java/org/apache/geode/internal/logging/LogService.java
@@ -54,8 +54,11 @@ public class LogService extends LogManager {
   public static final String GEMFIRE_VERBOSE_FILTER = "{GEMFIRE_VERBOSE}";
   public static final String DEFAULT_CONFIG = "/log4j2.xml";
   public static final String CLI_CONFIG = "/log4j2-cli.xml";
+
   protected static final String STDOUT = "STDOUT";
+
   private static final PropertyChangeListener propertyChangeListener = new 
PropertyChangeListenerImpl();
+
   /**
* Name of variable that is set to "true" in log4j2.xml to indicate that it 
is the default geode config xml.
*/
@@ -75,8 +78,7 @@ public class LogService extends LogManager {
   }
 
   private static void init() {
-LoggerContext context = ((org.apache.logging.log4j.core.Logger) 
LogManager.getLogger(BASE_LOGGER_NAME, 
GemFireParameterizedMessageFactory.INSTANCE))
-  .getContext();
+LoggerContext context = ((org.apache.logging.log4j.core.Logger) 
LogManager.getLogger(BASE_LOGGER_NAME, 
GemFireParameterizedMessageFactory.INSTANCE)).getContext();
 context.removePropertyChangeListener(propertyChangeListener);
 context.addPropertyChangeListener(propertyChangeListener);
 context.reconfigure(); // propertyChangeListener invokes 
configureFastLoggerDelegating
@@ -107,9 +109,7 @@ public class LogService extends LogManager {
   }
 
   public static boolean isUsingGemFireDefaultConfig() {
-final Configuration config = ((org.apache.logging.log4j.core.Logger) 
LogManager.getLogger(ROOT_LOGGER_NAME, 
GemFireParameterizedMessageFactory.INSTANCE))
-  .getContext()
-  .getConfiguration();
+final Configuration config = ((org.apache.logging.log4j.core.Logger) 
LogManager.getLogger(ROOT_LOGGER_NAME, 
GemFireParameterizedMessageFactory.INSTANCE)).getContext().getConfiguration();
 
 final StrSubstitutor sub = config.getStrSubstitutor();
 final StrLookup resolver = sub.getVariableResolver();
@@ -127,6 +127,7 @@ public class LogService extends LogManager {
* Finds a Log4j configuration file in the current directory.  The names of
* the files to look for are the same as those that Log4j would look for on
* the classpath.
+   *
* @return A File for the configuration file or null if one isn't found.
*/
   public static File findLog4jConfigInCurrentDir() {
@@ -135,6 +136,7 @@ public class LogService extends LogManager {
 
   /**
* Returns a Logger with the name of the calling class.
+   *
* @return The Logger for the calling class.
*/
   public static Logger getLogger() {
@@ -152,16 +154,16 @@ public class LogService extends LogManager {
* This is the bridge to LogWriter and LogWriterI18n that we need to 
eventually
* stop using in phase 1. We will switch over from a shared LogWriterLogger 
instance
* to having every GemFire class own its own private static GemFireLogger
+   *
* @return The LogWriterLogger for the calling class.
*/
-  public static LogWriterLogger createLogWriterLogger(final String name,
-  final String 
connectionName,
-  final boolean isSecure) {
+  public static LogWriterLogger createLogWriterLogger(final String name, final 
String connectionName, final boolean isSecure) {
 return 

[3/3] incubator-geode git commit: GEODE-1902: add ACCEPT and DENY tests for GEODE_VERBOSE and GEMFIRE_VERBOSE

[klund]

GEODE-1902: add ACCEPT and DENY tests for GEODE_VERBOSE and GEMFIRE_VERBOSE


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

Branch: refs/heads/develop
Commit: 375c6c5bcf3ee4ab52bb6bf4b34ca3eb26065ef9
Parents: 8703f2a
Author: Kirk Lund 
Authored: Tue Oct 4 13:11:03 2016 -0700
Committer: Kirk Lund 
Committed: Tue Oct 4 13:14:20 2016 -0700

--
 .../internal/logging/log4j/Configuration.java   |  29 +++
 .../GeodeVerboseLogMarkerIntegrationTest.java   | 217 +++
 .../logging/log4j/LogMarkerJUnitTest.java   | 112 --
 .../marker/log4j2-gemfire_verbose-accept.xml|  24 ++
 .../marker/log4j2-gemfire_verbose-deny.xml  |  24 ++
 .../marker/log4j2-geode_verbose-accept.xml  |  24 ++
 .../log4j/marker/log4j2-geode_verbose-deny.xml  |  24 ++
 7 files changed, 342 insertions(+), 112 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/375c6c5b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
--
diff --git 
a/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
 
b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
new file mode 100644
index 000..8f7ca1a
--- /dev/null
+++ 
b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/Configuration.java
@@ -0,0 +1,29 @@
+package org.apache.geode.internal.logging.log4j;
+
+import static org.assertj.core.api.Assertions.assertThat;
+
+import java.io.File;
+import java.io.FileOutputStream;
+import java.io.IOException;
+import java.net.URISyntaxException;
+import java.net.URL;
+
+import org.apache.commons.io.IOUtils;
+
+public class Configuration {
+
+  private URL resource;
+  private String configFileName;
+
+  public Configuration(final URL resource, final String configFileName) {
+this.resource = resource;
+this.configFileName = configFileName;
+  }
+
+  public File createConfigFileIn(final File targetFolder) throws IOException, 
URISyntaxException {
+File targetFile = new File(targetFolder, this.configFileName);
+IOUtils.copy(this.resource.openStream(), new FileOutputStream(targetFile));
+assertThat(targetFile).hasSameContentAs(new File(this.resource.toURI()));
+return targetFile;
+  }
+}

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/375c6c5b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/GeodeVerboseLogMarkerIntegrationTest.java
--
diff --git 
a/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/GeodeVerboseLogMarkerIntegrationTest.java
 
b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/GeodeVerboseLogMarkerIntegrationTest.java
new file mode 100644
index 000..c6f7b96
--- /dev/null
+++ 
b/geode-core/src/test/java/org/apache/geode/internal/logging/log4j/GeodeVerboseLogMarkerIntegrationTest.java
@@ -0,0 +1,217 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one or more
+ * contributor license agreements.  See the NOTICE file distributed with
+ * this work for additional information regarding copyright ownership.
+ * The ASF licenses this file to You under the Apache License, Version 2.0
+ * (the "License"); you may not use this file except in compliance with
+ * the License.  You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+package org.apache.geode.internal.logging.log4j;
+
+import static org.assertj.core.api.Assertions.*;
+
+import java.io.File;
+import java.io.IOException;
+import java.net.URISyntaxException;
+
+import org.apache.logging.log4j.Level;
+import org.apache.logging.log4j.Logger;
+import org.apache.logging.log4j.core.config.ConfigurationFactory;
+import org.apache.logging.log4j.status.StatusLogger;
+import org.junit.After;
+import org.junit.Before;
+import org.junit.Rule;
+import org.junit.Test;
+import org.junit.contrib.java.lang.system.SystemErrRule;
+import org.junit.contrib.java.lang.system.SystemOutRule;
+import org.junit.experimental.categories.Category;
+import org.junit.rules.TemporaryFolder;
+import org.junit.rules.TestName;
+
+import 

[49/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/basic_config/the_cache/intro_cache_management.html.md.erb
--
diff --git a/basic_config/the_cache/intro_cache_management.html.md.erb 
b/basic_config/the_cache/intro_cache_management.html.md.erb
deleted file mode 100644
index 2d21a60..000
--- a/basic_config/the_cache/intro_cache_management.html.md.erb
+++ /dev/null
@@ -1,79 +0,0 @@

-title:  Introduction to Cache Management

-
-The cache provides in-memory storage and management for your data.
-
-
-You organize your data in the cache into *data regions*, each with its own 
configurable behavior. You store your data into your regions in key/value pairs 
called *data entries*. The cache also provides features like transactions, data 
querying, disk storage management, and logging. See the Javadocs for 
`org.apache.geode.cache.Cache`.
-
-You generally configure caches using the `gfsh` command-line utility or a 
combination of XML declarations and API calls. Geode loads and processes your 
XML declarations when you first create the cache.
-
-Geode has one cache type for managing server and peer caches and one for 
managing client caches. The cache server process automatically creates its 
server cache at startup. In your application process, the cache creation 
returns an instance of the server/peer or client cache. From that point on, you 
manage the cache through API calls in your application.
-
-## The Caching APIs
-
-Geode's caching APIs provide specialized behavior for different system member 
types and security settings.
-
--   **`org.apache.geode.cache.RegionService`**. Generally, you use the 
`RegionService` functionality through instances of `Cache` and `ClientCache`. 
You only specifically use instances of `RegionService` for limited-access users 
in secure client applications that service many users. The `RegionService` API 
provides access to existing cache data regions and to the standard query 
service for the cache. For client caches, queries are sent to the server tier. 
For server and peer caches, queries are run in the current cache and any 
available peers. `RegionService` is implemented by `GemFireCache`.
--   **`org.apache.geode.cache.GemFireCache`**. You do not specifically use 
instances of `GemFireCache`, but you use `GemFireCache` functionality in your 
instances of `Cache` and `ClientCache`. `GemFireCache` extends `RegionService` 
and adds general caching features like region attributes, disk stores for 
region persistence and overflow, and access to the underlying distributed 
system. `GemFireCache` is implemented by `Cache` and `ClientCache`.
--   **`org.apache.geode.cache.Cache`**. Use the `Cache` interface to manage 
server and peer caches. You have one `Cache` per server or peer process. The 
`Cache` extends `GemFireCache` and adds server/peer caching features like 
communication within the distributed system, region creation, transactions and 
querying, and cache server functionality.
--   **`org.apache.geode≈setting_cache_initializer.cache.ClientCache`**. Use 
the `ClientCache` interface to manage the cache in your clients. You have one 
`ClientCache` per client process. The `ClientCache` extends `GemFireCache` and 
adds client-specific caching features like client region creation, subscription 
keep-alive management for durable clients, querying on server and client tiers, 
and RegionService creation for secure access by multiple users within the 
client.
-
-## The Cache XML
-
-Your `cache.xml` must be formatted according to the product XML schema 
definition `cache-1.0.xsd`. The schema definition file is available in the 
product distribution at 
`$GEMFIRE/schemas/geode.apache.org/schema/cache/cache-1.0.xsd`.
-
-You use one format for peer and server caches and another for client caches.
-
-`cache.xml` for Peer/Server:
-
-``` pre
-
-http://geode.incubator.apache.org/schema/cache;
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
-xsi:schemaLocation="http://geode.incubator.apache.org/schema/cache 
http://geode.incubator.apache.org/schema/cache/cache-1.0.xsd;
-version="1.0”>
-...
-
-```
-
-`cache.xml` for Client:
-
-``` pre
-
-http://geode.incubator.apache.org/schema/cache;
-xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
-xsi:schemaLocation="http://geode.incubator.apache.org/schema/cache 
http://geode.incubator.apache.org/schema/cache/cache-1.0.xsd;
-version="1.0”>
-...
-
-```
-
-For more information on the `cache.xml` file, see 
[cache.xml](../../reference/topics/chapter_overview_cache_xml.html#cache_xml).
-
-## Create and Close a Cache
-
-Your system configuration and cache configuration are initialized when you 
start your member processes and create each member’s Geode cache. If you are 
using the cluster configuration service, member processes can pick up its cache 
configuration from the cluster or group's current configuration. See 

[18/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/how_partitioning_works_2.svg
--
diff --git a/geode-docs/images_svg/how_partitioning_works_2.svg 
b/geode-docs/images_svg/how_partitioning_works_2.svg
new file mode 100644
index 000..6351a28
--- /dev/null
+++ b/geode-docs/images_svg/how_partitioning_works_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="68 212 385 412" 
width="385pt" height="412pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:43Zhow_it_works_2Layer 
1Partitioned Region ALogical ViewXYZPartitioned Region APh
 ysical ViewNo local 
dataMachine 1Partitioned Region 
AXMachine 
2Partitioned Region AYMachine 3Z

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/http_module_cs_with_locator.svg
--
diff --git a/geode-docs/images_svg/http_module_cs_with_locator.svg 
b/geode-docs/images_svg/http_module_cs_with_locator.svg
new file mode 100644
index 000..3b8e6a3
--- /dev/null
+++ b/geode-docs/images_svg/http_module_cs_with_locator.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="77 333 373 279" 
width="373pt" height="279pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:40Zcs with 
locatorLayer 1Partitioned <
 /tspan>Session 
DataPartitioned Session DataServerServerPartitioned Session Data
 Application Server 
InstanceClientapp server requestsLocal Cacheconnection 
poolLocatorprovides discovery and load balancing 
servicesPartitioned 
Session 
Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/http_module_p2p_with_locator.svg
--
diff --git a/geode-docs/images_svg/http_module_p2p_with_locator.svg 
b/geode-docs/images_svg/http_module_p2p_with_locator.svg
new file mode 100644
index 000..3c7c0b4
--- /dev/null
+++ b/geode-docs/images_svg/http_module_p2p_with_locator.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="59 348 499 191" 
width="499pt" height="191pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:39Zp2p with 
locatorLayer 1Application Server InstanceCacheApplication Server InstanceCacheApplication Server InstanceCacheapp server 
requestsapp server 
requestsapp server 
requestsReplicated 
Session 
DataReplicated Session DataReplicated Session DataLocatorprovides discovery and load 
balancing services

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/locator_discovery.svg
--
diff --git a/geode-docs/images_svg/locator_discovery.svg 
b/geode-docs/images_svg/locator_discovery.svg
new file mode 100644
index 000..53e9f3b
--- /dev/null
+++ b/geode-docs/images_svg/locator_discovery.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="81 317 450 160" 
width="450pt" height="160pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:26ZlocatorsLayer 1PeerPeerPeer Discovery Using 
Locators LocatorPeerLocatorCache DataCache DataCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/member_severe_alert.svg
--
diff --git a/geode-docs/images_svg/member_severe_alert.svg 
b/geode-docs/images_svg/member_severe_alert.svg
new file mode 100644
index 000..8614503
--- /dev/null
+++ b/geode-docs/images_svg/member_severe_alert.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="94 248 368 267" 
width="368pt" height="267pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:59Zmember severe 
alertLayer 11. CACHE_OPERATIONCache ServerReplicated RegionCache 
ServerReplicated 
RegionLocatorClientx="12.466797" y="10" textLength="25.566406">Clientx1="346.5" y1="461.25" x2="346.5" y2="421.948" 
 >marker-end="url(#FilledArrow_Marker)" stroke="#252525" stroke-linecap="round" 
 >stroke-linejoin="round" stroke-width=".7203"/>d="M 323.91 461.25 L 369.09 461.25 C 372.76822 461.25 375.75 464.23178 375.75 
 >467.91 L 375.75 490.59 C 375.75 494.26822 372.76822 497.25 369.09 497.25 L 
 

[19/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/hibernate_cs.svg
--
diff --git a/geode-docs/images_svg/hibernate_cs.svg 
b/geode-docs/images_svg/hibernate_cs.svg
new file mode 100644
index 000..ce9c3a8
--- /dev/null
+++ b/geode-docs/images_svg/hibernate_cs.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="59 233 493 205" 
width="493pt" height="205pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:24ZcsLayer 
1Partitioned Session DataPartitioned Session DataPartitioned 
Session 
DataServerServerServerPartitioned DataHibernate 
SessionClientaccess to Hibernate entitiesconnection poolIf data not found in cache, Hibernate accesses database...RelationalDatabasePartitioned DataPartitioned Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/hibernate_overview.svg
--
diff --git a/geode-docs/images_svg/hibernate_overview.svg 
b/geode-docs/images_svg/hibernate_overview.svg
new file mode 100644
index 000..0fd8669
--- /dev/null
+++ b/geode-docs/images_svg/hibernate_overview.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="146 287 389 228" 
width="389pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:06ZoverviewLayer 1Cached DataCached DataMemberHibernate 
SessionMemberCached Dataaccess to Hibernate entitiesIf data not found in cache, Hibernate accesses 
database...RelationalDatabaseCached Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/hibernate_p2p.svg
--
diff --git a/geode-docs/images_svg/hibernate_p2p.svg 
b/geode-docs/images_svg/hibernate_p2p.svg
new file mode 100644
index 000..bc536dc
--- /dev/null
+++ b/geode-docs/images_svg/hibernate_p2p.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="59 269 499 228" 
width="499pt" height="19pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:09Zp2pLayer 1stroke="#252525" stroke-linecap="round" stroke-linejoin="round" 
 >stroke-width=".7203"/>fill="black">fill="black" x="27.143066" y="10" textLength="81.713867">Hibernate 
 >SessionPeer CacheHibernate 
SessionPeer CacheHibernate SessionPeer CacheReplicated DataReplicated DataReplicated
  Dataaccess 
to Hibernate entitiesaccess to Hibernate entitiesaccess to Hibernate entitiesIf data not found in cache, Hibernate accesses 
database...RelationalDatabase

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/how_partitioning_works_1.svg
--
diff --git a/geode-docs/images_svg/how_partitioning_works_1.svg 
b/geode-docs/images_svg/how_partitioning_works_1.svg
new file mode 100644
index 000..b7cd2a2
--- /dev/null
+++ b/geode-docs/images_svg/how_partitioning_works_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="181 308 386 413" 
width="386pt" height="413pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:44Zhow_it_works_1Layer 
1Partitioned Region ALogical ViewXYZPartitioned Region APhysical ViewXMachine 1P
 artitioned Region AYMachine 2Partitioned Region AZMachine 3

[31/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb 
b/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb
new file mode 100644
index 000..56e65e1
--- /dev/null
+++ b/geode-docs/developing/partitioned_regions/chapter_overview.html.md.erb
@@ -0,0 +1,43 @@
+---
+title:  Partitioned Regions
+---
+
+In addition to basic region management, partitioned regions include options 
for high availability, data location control, and data balancing across the 
distributed system.
+
+-   **[Understanding 
Partitioning](../../developing/partitioned_regions/how_partitioning_works.html)**
+
+To use partitioned regions, you should understand how they work and your 
options for managing them.
+
+-   **[Configuring Partitioned 
Regions](../../developing/partitioned_regions/managing_partitioned_regions.html)**
+
+Plan the configuration and ongoing management of your partitioned region 
for host and accessor members and configure the regions for startup.
+
+-   **[Configuring the Number of Buckets for a Partitioned 
Region](../../developing/partitioned_regions/configuring_bucket_for_pr.html)**
+
+Decide how many buckets to assign to your partitioned region and set the 
configuration accordingly.
+
+-   **[Custom-Partitioning and Colocating 
Data](../../developing/partitioned_regions/overview_custom_partitioning_and_data_colocation.html)**
+
+You can customize how Apache Geode groups your partitioned region data 
with custom partitioning and data colocation.
+
+-   **[Configuring High Availability for Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_ha_works.html)**
+
+By default, Apache Geode stores only a single copy of your partitioned 
region data among the region's data stores. You can configure Geode to maintain 
redundant copies of your partitioned region data for high availability.
+
+-   **[Configuring Single-Hop Client Access to Server-Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_single_hop_works.html)**
+
+Single-hop data access enables the client pool to track where a 
partitioned region’s data is hosted in the servers. To access a single entry, 
the client directly contacts the server that hosts the key, in a single hop.
+
+-   **[Rebalancing Partitioned Region 
Data](../../developing/partitioned_regions/rebalancing_pr_data.html)**
+
+In a distributed system with minimal contention to the concurrent threads 
reading or updating from the members, you can use rebalancing to dynamically 
increase or decrease your data and processing capacity.
+
+-   **[Checking Redundancy in Partitioned 
Regions](../../developing/partitioned_regions/checking_region_redundancy.html)**
+
+Under some circumstances, it can be important to verify that your 
partitioned region data is redundant and that upon member restart, redundancy 
has been recovered properly across partitioned region members.
+
+-   **[Moving Partitioned Region Data to Another 
Member](../../developing/partitioned_regions/moving_partitioned_data.html)**
+
+You can use the `PartitionRegionHelper` `moveBucketByKey` and `moveData` 
methods to explicitly move partitioned region data from one member to another.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
--
diff --git 
a/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
 
b/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
new file mode 100644
index 000..a35de98
--- /dev/null
+++ 
b/geode-docs/developing/partitioned_regions/checking_region_redundancy.html.md.erb
@@ -0,0 +1,38 @@
+---
+title:  Checking Redundancy in Partitioned Regions
+---
+
+Under some circumstances, it can be important to verify that your partitioned 
region data is redundant and that upon member restart, redundancy has been 
recovered properly across partitioned region members.
+
+You can verify partitioned region redundancy by making sure that the 
`numBucketsWithoutRedundancy` statistic is **zero** for all your partitioned 
regions. To check this statistic, use the following `gfsh` command:
+
+``` pre
+gfsh>show metrics --categories=partition --region=region_name
+```
+
+For example:
+
+``` pre
+gfsh>show metrics --categories=partition --region=posts
+
+Cluster-wide Region Metrics
+- | --- | -
+partition | putLocalRate| 0
+  | putRemoteRate   | 0
+  | putRemoteLatency| 0
+  | putRemoteAvgLatency | 0
+  | bucketCount | 1
+ 

[09/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
--
diff --git 
a/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb 
b/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
new file mode 100644
index 000..89e7178
--- /dev/null
+++ b/geode-docs/managing/disk_storage/file_names_and_extensions.html.md.erb
@@ -0,0 +1,79 @@
+---
+title:  Disk Store File Names and Extensions
+---
+
+Disk store files include store management files, access control files, and the 
operation log, or oplog, files, consisting of one file for deletions and 
another for all other operations.
+
+
+The next tables describe file names and extensions; they are followed by 
example disk store files.
+
+## File Names
+
+File names have three parts:
+
+**First Part of File Name: Usage Identifier**
+
+| Values   | Used for  
 | Examples   |
+|--|||
+| OVERFLOW | Oplog data from overflow regions and queues only. 
 | OVERFLOWoverflowDS1\_1.crf |
+| BACKUP   | Oplog data from persistent and persistent+overflow regions and 
queues. | BACKUPoverflowDS1.if, BACKUPDEFAULT.if |
+| DRLK\_IF | Access control - locking the disk store.  
 | DRLK\_IFoverflowDS1.lk, DRLK\_IFDEFAULT.lk |
+
+**Second Part of File Name: Disk Store Name**
+
+| Values  | Used for   
   | 
Examples
 |
+|-|---|--|
+| disk store name | Non-default disk stores.   
   | 
name="overflowDS1" DRLK\_IFoverflowDS1.lk, name="persistDS1" 
BACKUPpersistDS1\_1.crf |
+| DEFAULT | Default disk store name, used when persistence or 
overflow are specified on a region or queue but no disk store is named. | 
DRLK\_IFDEFAULT.lk, BACKUPDEFAULT\_1.crf
 |
+
+**Third Part of File Name: oplog Sequence Number**
+
+| Values| Used for 
   | Examples   
  |
+|---|-|--|
+| Sequence number in the format \_n | Oplog data files only. Numbering starts 
with 1. | OVERFLOWoverflowDS1\_1.crf, BACKUPpersistDS1\_2.crf, 
BACKUPpersistDS1\_3.crf |
+
+## File Extensions
+
+| File extension | Used for | Notes

|
+||--|--|
+| if | Disk store metadata  | Stored 
in the first disk-dir listed for the store. Negligible size - not considered in 
size control. |
+| lk | Disk store access control| Stored 
in the first disk-dir listed for the store. Negligible size - not considered in 
size control. |
+| crf| Oplog: create, update, and invalidate operations | 
Pre-allocated 90% of the total max-oplog-size at creation.  
 |
+| drf| Oplog: delete operations | 
Pre-allocated 10% of the total max-oplog-size at creation.  
 |
+| krf| Oplog: key and crf offset information| Created 
after the oplog has reached the max-oplog-size. Used to improve performance at 
startup.  |
+
+Example files for disk stores persistDS1 and overflowDS1:
+
+``` pre
+bash-2.05$ ls -tlra persistData1/
+total 8
+-rw-rw-r--   1 person users188 Mar  4 06:17 BACKUPpersistDS1.if
+drwxrwxr-x   2 person users512 Mar  4 06:17 .
+-rw-rw-r--   1 person users  0 Mar  4 06:18 BACKUPpersistDS1_1.drf
+-rw-rw-r--   1 person users 38 Mar  4 06:18 BACKUPpersistDS1_1.crf
+drwxrwxr-x   8 person users512 Mar  4 06:20 ..
+bash-2.05$
+ 
+bash-2.05$ ls -ltra overflowData1/
+total 1028
+drwxrwxr-x   8 

[38/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
--
diff --git 
a/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
 
b/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
new file mode 100644
index 000..d809635
--- /dev/null
+++ 
b/geode-docs/basic_config/data_entries_custom_classes/managing_data_entries.html.md.erb
@@ -0,0 +1,129 @@
+---
+title:  Managing Data Entries
+---
+
+Program your applications to create, modify, and manage your cached data 
entries.
+
+
+**Note:**
+If you do not have the cache's `copy-on-read` attribute set to true, do not 
change the objects returned from the Java entry access methods. Instead, create 
a copy of the object, then modify the copy and pass it to the Java `put` 
method. Modifying a value in place bypasses the entire distribution framework 
provided by Geode, including cache listeners and expiration activities, and can 
produce undesired results.
+
+## Basic Create and Update
+
+To create or update an entry in the cache, use `Region.put`. For example:
+
+``` pre
+String name = ... 
+String value = ...  
+this.currRegion.put(name,value); 
+```
+
+**Note:**
+You can also use the `gfsh put` command to add entries to a region, and the 
`get` command to retrieve entries from a region. See 
[get](../../tools_modules/gfsh/command-pages/get.html) and 
[put](../../tools_modules/gfsh/command-pages/put.html) for more information.
+
+If you want only to create the entry (with a null value and with method 
failure if the entry already exists), use `Region.create` instead.
+
+## Batch Operations (getAll, putAll, removeAll)
+
+Geode provides three APIs to perform batch operations on multiple region 
entries:
+
+-   `Region.getAll`
+-   `Region.putAll`
+-   `Region.removeAll`
+
+The `getAll` method takes a collection of keys and returns a `Map` of values 
for the provided keys. If a given key does not exist in the region, then that 
key's value in the returned map will be null.
+
+The `putAll` method takes a `Map` of key-value pairs and puts them into the 
cache and distributes them in a single operation.
+
+**Example:**
+
+``` pre
+void putAll(String command) throws CacheException 
+{ 
+// Get Entry keys and values into Strings key1, ... keyN and value1, ... 
valueN 
+  Map map = new LinkedHashMap(); 
+  map.put(key1, value1)); 
+  ...
+  map.put(keyN, valueN));
+  this.currRegion.putAll(map); 
+}
+```
+
+The updates to the cache are done individually in the order in which they were 
placed in the `Map`. For partitioned regions, multiple events are sent as a 
single message to the primary buckets and then distributed to the secondary 
buckets.
+
+**Note:**
+The processing of maps with very many entries and/or very large data may 
affect system performance and cause cache update timeouts, especially if the 
region uses overflow or persistence to disk.
+
+The `removeAll` method takes a collection of keys and removes all of the 
entries for the specified keys from this region. This call performs the 
equivalent of calling`destroy(Object)` on this region once for each key in the 
specified collection. If an entry does not exist, then that key is skipped. An 
`EntryNotFoundException` is not thrown. This operation will be distributed to 
other caches if the region's scope is not set to `Scope.LOCAL`.
+
+## Safe Entry Modification
+
+When you get an entry value from the cache, by default, the retrieval methods 
return a direct reference to the cached object. This provides the value as 
quickly as possible, but also opens the cache to direct, in-place changes.
+
+**Note:**
+Do not directly modify cached values. Modifying a value in place bypasses the 
Geode distribution framework, including cache writers and listeners, expiration 
activities, and transaction management, and can produce undesired results.
+
+Always change your entries using copies of the retrieved objects—never 
directly modify the returned objects. You can do this in one of two ways:
+
+1.  Change the entry retrieval behavior for your cache by setting the cache 
attribute, `copy-on-read`, to true (the default is false).
+
+``` pre
+
+ ...
+
+```
+
+When `copy-on-read` is true, the entry access methods return copies of the 
entries. This protects you from inadvertently modifying in-place, but 
negatively impacts performance and memory consumption when copying is not 
needed.
+
+These entry access methods return an entry reference if `copy-on-read` is 
false and a copy of the entry if `copy-on-read` is true:
+
+`Region.get`
+result of `Region.put`
+`EntryEvent.getNewValue`
+`Region.values`
+`Region.Entry.getValue`
+`EntryEvent.getOldValue`
+`Query.select`
+
+2.  Create a copy of the returned object and work with that. For 

[29/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
--
diff --git 
a/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
 
b/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
new file mode 100644
index 000..a834b60
--- /dev/null
+++ 
b/geode-docs/developing/query_index/using_indexes_with_equijoin_queries_multiple_regions.html.md.erb
@@ -0,0 +1,62 @@
+---
+title:  Using Indexes on Equi-Join Queries using Multiple Regions
+---
+
+To query across multiple regions, identify all equi-join conditions. Then, 
create as few indexes for the equi-join conditions as you can while still 
joining all regions.
+
+
+If there are equi-join conditions that redundantly join two regions (in order 
to more finely filter the data, for example), then creating redundant indexes 
for these joins will negatively impact performance. Create indexes only on one 
equi-join condition for each region pair.
+
+In this example query:
+
+``` pre
+SELECT DISTINCT * 
+FROM /investors inv, /securities sc, /orders or, 
+inv.ordersPlaced inv_op, or.securities or_sec 
+WHERE inv_op.orderID = or.orderID 
+AND or_sec.secID = sc.secID
+```
+
+All conditions are required to join the regions, so you would create four 
indexes, two for each equi-join condition:
+
+| FROM clause  | Indexed expression |
+|--||
+| /investors inv, inv.ordersPlaced inv\_op | inv\_op.orderID|
+| /orders or, or.securities or\_sec| or.orderID |
+
+| FROM clause   | Indexed expression |
+|---||
+| /orders or, or.securities or\_sec | or\_sec.secID  |
+| /securities sc| sc.secID   |
+
+Adding another condition to the example:
+
+``` pre
+SELECT DISTINCT * 
+FROM /investors inv, /securities sc, /orders or, 
+inv.ordersPlaced inv_op, or.securities or_sec, sc.investors sc_invs 
+WHERE inv_op.orderID = or.orderID 
+AND or_sec.secID = sc.secID
+AND inv.investorID = sc_invs.investorID
+```
+
+You would still only want to use four indexes in all, as that's all you need 
to join all of the regions. You would need to choose the most performant two of 
the following three index pairs:
+
+| FROM clause  | Indexed expression |
+|--||
+| /investors inv, inv.ordersPlaced inv\_op | inv\_op.orderID|
+| /orders or, or.securities or\_sec| or.orderID |
+
+| FROM clause   | Indexed expression |
+|---||
+| /orders or, or.securities or\_sec | or\_sec.secID  |
+| /securities sc, sc.investors sc\_invs | sc.secID   |
+
+| FROM clause  | Indexed expression  |
+|--|-|
+| /investors inv, inv.ordersPlaced inv\_op | inv.investorID  |
+| /securities sc, sc.investors sc\_invs| sc\_invs.investorID |
+
+The most performant set is that which narrows the data to the smallest result 
set possible. Examine your data and experiment with the three index pairs to 
see which provides the best performance.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_select/aggregates.html.md.erb
--
diff --git a/geode-docs/developing/query_select/aggregates.html.md.erb 
b/geode-docs/developing/query_select/aggregates.html.md.erb
new file mode 100644
index 000..1a4e0aa
--- /dev/null
+++ b/geode-docs/developing/query_select/aggregates.html.md.erb
@@ -0,0 +1,92 @@
+---
+title:  OQL Aggregate Functions
+---
+
+The aggregate functions 
+```MIN```,
+```MAX```,
+```AVG```,
+```AVG``` over a DISTINCT expression,
+```SUM``` over a DISTINCT expression,
+```COUNT```, and
+```COUNT``` over a DISTINCT expression
+are supported.
+The ```GROUP BY``` extension is also supported where appropriate.
+
+The ```MIN``` function returns the smallest of the selected
+expression.
+The type of the expression must evaluate to a 
+```java.lang.Comparable```.
+
+The ```MAX``` function returns the largest of the selected
+expression.
+The type of the expression must evaluate to a 
+```java.lang.Comparable```.
+
+The ```AVG``` function returns the arithmetic mean of the set
+formed by the selected expression.
+The type of the expression must evaluate to a 
+```java.lang.Number```.
+For partitioned regions,
+each node's buckets provide both a sum and the number of elements
+to the node executing the query,
+such that a correct 

[42/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/query_additional/case_sensitivity.html.md.erb
--
diff --git a/developing/query_additional/case_sensitivity.html.md.erb 
b/developing/query_additional/case_sensitivity.html.md.erb
deleted file mode 100644
index 2d49259..000
--- a/developing/query_additional/case_sensitivity.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@

-title:  Case Sensitivity

-
-Query language keywords such as SELECT, NULL, DATE, and TRACE are 
case-insensitive. Identifiers such as attribute names, method names, and path 
expressions are case-sensitive.
-
-In terms of query string and region entry matching, if you want to perform a 
case-insensitive search on a particular field, you can use the Java String 
class `toUpperCase` and `toLowerCase` methods in your query. For example:
-
-``` pre
-SELECT entry.value FROM /exampleRegion.entries entry WHERE 
entry.value.toUpperCase LIKE '%BAR%'
-```
-
-or
-
-``` pre
-SELECT * FROM /exampleRegion WHERE foo.toLowerCase LIKE '%bar%'
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/query_additional/literals.html.md.erb
--
diff --git a/developing/query_additional/literals.html.md.erb 
b/developing/query_additional/literals.html.md.erb
deleted file mode 100644
index 37fcc0f..000
--- a/developing/query_additional/literals.html.md.erb
+++ /dev/null
@@ -1,65 +0,0 @@

-title:  Supported Literals

-
-## Comparing Values With java.util.Date
-
-Geode supports the following literal types:
-
-**boolean**
-A `boolean` value, either TRUE or FALSE
-**int** and **long**
-An integer literal is of type `long` if has a suffix of the ASCII letter 
L. Otherwise it is of type `int`.
-**floating point**
-A floating-point literal is of type `float` if it has a suffix of an ASCII 
letter `F`. Otherwise its type is `double`. Optionally, it can have a suffix of 
an ASCII letter `D`. A double or floating point literal can optionally include 
an exponent suffix of `E` or `e`, followed by a signed or unsigned number.
-
-**string**
-String literals are delimited by single quotation marks. Embedded 
single-quotation marks are doubled. For example, the character string `'Hello'` 
evaluates to the value `Hello`, while the character string `'He said, 
''Hello'''` evaluates to `He said, 'Hello'`. Embedded newlines are kept as part 
of the string literal.
-**char**
-A literal is of type char if it is a string literal prefixed by the 
keyword `CHAR`, otherwise it is of type `string`. The `CHAR` literal for the 
single-quotation mark character is `CHAR` `` (four single quotation 
marks).
-**date**
-A `java.sql.Date` object that uses the JDBC format prefixed with the DATE 
keyword: `DATE -mm-dd`. In the `Date`, `` represents the year, `mm` 
represents the month, and `dd` represents the day. The year must be represented 
by four digits; a two-digit shorthand for the year is not allowed.
-**time**
-A `java.sql.Time` object that uses the JDBC format (based on a 24-hour 
clock) prefixed with the TIME keyword: `TIME hh:mm:ss`. In the `Time`, `hh` 
represents the hours, `mm` represents the minutes, and `ss` represents the 
seconds.
-**timestamp**
-A `java.sql.Timestamp` object that uses the JDBC format with a TIMESTAMP 
prefix: `TIMESTAMP -mm-dd hh:mm:ss.f` In the `Timestamp`, 
`-mm-dd` represents the `date`, `hh:mm:ss` represents the `time`, and 
`f` represents the fractional seconds (up to nine digits).
-**NIL**
-Equivalent alternative of `NULL`.
-**NULL**
-The same as `null` in Java.
-**UNDEFINED**
-A special literal that is a valid value for any data type. An `UNDEFINED` 
value is the result of accessing an attribute of a null-valued attribute. Note 
that if you access an attribute that has an explicit value of null, then it is 
not undefined. For example if a query accesses the attribute address.city and 
address is null, the result is undefined. If the query accesses address, then 
the result is not undefined, it is `NULL`.
-
-You can compare temporal literal values `DATE`, `TIME`, and `TIMESTAMP` with 
`java.util.Date` values. There is no literal for `java.util.Date` in the query 
language.
-
-## Type Conversion
-
-The Geode query processor performs implicit type conversions and promotions 
under certain cases in order to evaluate expressions that contain different 
types. The query processor performs binary numeric promotion, method invocation 
conversion, and temporal type conversion.
-
-## Binary Numeric Promotion
-
-The query processor performs binary numeric promotion on the operands of the 
following operators:
-
--   Comparison operators , =, , and =
--   Equality operators = and 
--   Binary numeric promotion widens the operands in a numeric expression to 
the widest representation used by any of the operands. In each 

[26/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/getting_started/book_intro.html.md.erb
--
diff --git a/geode-docs/getting_started/book_intro.html.md.erb 
b/geode-docs/getting_started/book_intro.html.md.erb
new file mode 100644
index 000..05c946c
--- /dev/null
+++ b/geode-docs/getting_started/book_intro.html.md.erb
@@ -0,0 +1,23 @@
+---
+title:  Getting Started with Apache Geode
+---
+
+A tutorial demonstrates features, and a main features section describes key 
functionality.
+
+-   **[About Apache Geode](geode_overview.html)**
+
+Apache Geode is a data management platform that provides real-time, 
consistent access to data-intensive applications throughout widely distributed 
cloud architectures.
+
+-   **[Main Features of Apache Geode](product_intro.html)**
+
+This section summarizes the main features and key functionality of Apache 
Geode.
+
+-   **[Prerequisites and Installation 
Instructions](../prereq_and_install.html)**
+
+Each host of Apache Geode 1.0.0-incubating that meets a small set of 
prerequisites may follow the provided installation instructions.
+
+-   **[Apache Geode in 15 Minutes or Less](15_minute_quickstart_gfsh.html)**
+
+Need a quick introduction to Apache Geode? Take this brief tour to try out 
basic features and functionality.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/getting_started/geode_overview.html.md.erb
--
diff --git a/geode-docs/getting_started/geode_overview.html.md.erb 
b/geode-docs/getting_started/geode_overview.html.md.erb
new file mode 100644
index 000..dca502c
--- /dev/null
+++ b/geode-docs/getting_started/geode_overview.html.md.erb
@@ -0,0 +1,20 @@
+---
+title:  About Apache Geode
+---
+
+Apache Geode is a data management platform that provides real-time, consistent 
access to data-intensive applications throughout widely distributed cloud 
architectures.
+
+
+Geode pools memory, CPU, network resources, and optionally local disk across 
multiple processes to manage application objects and behavior. It uses dynamic 
replication and data partitioning techniques to implement high availability, 
improved performance, scalability, and fault tolerance. In addition to being a 
distributed data container, Geode is an in-memory data management system that 
provides reliable asynchronous event notifications and guaranteed message 
delivery.
+
+## Main Concepts and Components
+
+*Caches* are an abstraction that describe a node in a Geode distributed 
system. Application architects can arrange these nodes in peer-to-peer or 
client/server topologies.
+
+Within each cache, you define data *regions*. Data regions are analogous to 
tables in a relational database and manage data in a distributed fashion as 
name/value pairs. A *replicated* region stores identical copies of the data on 
each cache member of a distributed system. A *partitioned* region spreads the 
data among cache members. After the system is configured, client applications 
can access the distributed data in regions without knowledge of the underlying 
system architecture. You can define listeners to create notifications about 
when data has changed, and you can define expiration criteria to delete 
obsolete data in a region.
+
+For large production systems, Geode provides *locators*. Locators provide both 
discovery and load balancing services. You configure clients with a list of 
locator services and the locators maintain a dynamic list of member servers. By 
default, Geode clients and servers use port 40404 to discover each other.
+
+
+
+For more information on product features, see [Main Features of Apache 
Geode](product_intro.html).

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/getting_started/installation/install_standalone.html.md.erb
--
diff --git 
a/geode-docs/getting_started/installation/install_standalone.html.md.erb 
b/geode-docs/getting_started/installation/install_standalone.html.md.erb
new file mode 100644
index 000..22936c7
--- /dev/null
+++ b/geode-docs/getting_started/installation/install_standalone.html.md.erb
@@ -0,0 +1,121 @@
+---
+title:  How to Install
+---
+
+Build from source or use the ZIP or TAR distribution to install Apache Geode 
on every physical and virtual machine that will run Apache Geode.
+
+## Build from Source on Unix
+
+1.  Set the JAVA\_HOME environment variable.
+
+``` pre
+JAVA_HOME=/usr/java/jdk1.8.0_60
+export JAVA_HOME
+```
+
+2.  Download the project source from the Releases page found at 
[http://geode.incubator.apache.org](http://geode.incubator.apache.org/), and 
unpack the source code.
+3.  Within the directory containing the unpacked source code, build without 
tests:
+
+``` pre
+$ ./gradlew build 

[44/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/events/limit_server_subscription_queue_size.html.md.erb
--
diff --git a/developing/events/limit_server_subscription_queue_size.html.md.erb 
b/developing/events/limit_server_subscription_queue_size.html.md.erb
deleted file mode 100644
index ff571b2..000
--- a/developing/events/limit_server_subscription_queue_size.html.md.erb
+++ /dev/null
@@ -1,57 +0,0 @@

-title:  Limit the Server's Subscription Queue Memory Use

-
-
-These are options for limiting the amount of server memory the subscription 
queues consume.
-
--   Optional: Conflate the subscription queue messages.
--   Optional: Increase the frequency of queue synchronization. This only 
applies to configurations where server redundancy is used for high 
availability. Increase the client’s pool configuration, 
`subscription-ack-interval`. The client periodically sends a batch 
acknowledgment of messages to the server, rather than acknowledging each 
message individually. A lower setting speeds message delivery and generally 
reduces traffic between the server and client. A higher setting helps contain 
server queue size. Example:
-
-``` pre
-
- 
-   
-  ... 
-
-```
-
-You might want to lower the interval if you have a very busy system and 
want to reduce the space required in the servers for the subscription queues. 
More frequent acknowledgments means fewer events held in the server queues 
awaiting acknowledgment.
-
--   Optional: Limit Queue Size. Cap the server queue size using overflow or 
blocking. These options help avoid out of memory errors on the server in the 
case of slow clients. A slow client slows the rate that the server can send 
messages, causing messages to back up in the queue, possibly leading to out of 
memory on the server. You can use one or the other of these options, but not 
both:
--   Optional: Overflow to Disk. Configure subscription queue overflow by 
setting the server’s `client-subscription` properties. With overflow, the 
most recently used (MRU) events are written out to disk, keeping the oldest 
events, the ones that are next in line to be sent to the client, available in 
memory. Example:
-
-``` pre
-
- 
-   
-
-```
-
--   Optional: Block While Queue Full. Set the server’s 
`maximum-message-count` to the maximum number of event messages allowed in any 
single subscription queue before incoming messages are blocked. You can only 
limit the message count, not the size allocated for messages. Examples:
-
-XML:
-
-``` pre
-
-  
-```
-
-API:
-
-``` pre
-Cache cache = ...; 
-CacheServer cacheServer = cache.addCacheServer(); 
-cacheServer.setPort(41414); 
-cacheServer.setMaximumMessageCount(5); 
-cacheServer.start(); 
-```
-
-**Note:**
-With this setting, one slow client can slow the server and all of its 
other clients because this blocks the threads that write to the queues. All 
operations that add messages to the queue block until the queue size drops to 
an acceptable level. If the regions feeding these queues are partitioned or 
have `distributed-ack` or `global` scope, operations on them remain blocked 
until their event messages can be added to the queue. If you are using this 
option and see stalling on your server region operations, your queue capacity 
might be too low for your application behavior.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/events/list_of_event_handlers_and_events.html.md.erb
--
diff --git a/developing/events/list_of_event_handlers_and_events.html.md.erb 
b/developing/events/list_of_event_handlers_and_events.html.md.erb
deleted file mode 100644
index 5f63db1..000
--- a/developing/events/list_of_event_handlers_and_events.html.md.erb
+++ /dev/null
@@ -1,164 +0,0 @@

-title:  List of Event Handlers and Events

-
-Geode provides many types of events and event handlers to help you manage your 
different data and application needs.
-
-## Event Handlers
-
-Use either cache handlers or membership handlers in any single application. Do 
not use both. The event handlers in this table are cache handlers unless 
otherwise noted.
-
-
-
-
-
-
-
-
-
-Handler API
-Events received
-Description
-
-
-
-
-AsyncEventListener
-AsyncEvent
-Tracks changes in a region for write-behind processing. Extends th 
CacheCallback interface. You install a 
write-back cache listener to an AsyncEventQueue 
instance. You can then add the AsyncEventQueue 
instance to one or more regions for write-behind processing. See [Implementing 
an AsyncEventListener for Write-Behind Cache Event 

[33/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb
--
diff --git 
a/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb 
b/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb
new file mode 100644
index 000..f61aba6
--- /dev/null
+++ b/geode-docs/developing/events/ha_event_messaging_whats_next.html.md.erb
@@ -0,0 +1,78 @@
+---
+title:  Highly Available Client/Server Event Messaging
+---
+
+
+With server redundancy, each pool has a primary server and some number of 
secondaries. The primaries and secondaries are assigned on a per-pool basis and 
are generally spread out for load balancing, so a single client with multiple 
pools may have primary queues in more than one server.
+
+The primary server pushes events to clients and the secondaries maintain queue 
backups. If the primary server fails, one of the secondaries becomes primary to 
provide uninterrupted event messaging.
+
+For example, if there are six servers running and `subscription-redundancy` is 
set to two, one server is the primary, two servers are secondary, and the 
remaining three do not actively participate in HA for the client. If the 
primary server fails, the system assigns one of the secondaries as the new 
primary and attempts to add another server to the secondary pool to retain the 
initial redundancy level. If no new secondary server is found, then the 
redundancy level is not satisfied but the failover procedure completes 
successfully. As soon as another secondary is available, it is added.
+
+When high availability is enabled:
+
+-   The primary server sends event messages to the clients.
+-   Periodically, the clients send received messages to the server and the 
server removes the sent messages from its queues.
+-   Periodically, the primary server synchronizes with its secondaries, 
notifying them of messages that can be discarded because they have already been 
sent and received. There is a lag in notification, so the secondary servers 
remain only roughly synchronized with the primary. Secondary queues contain all 
messages that are contained in the primary queue plus possibly a few messages 
that have already been sent to clients.
+-   In the case of primary server failure, one of the secondaries becomes the 
primary and begins sending event messages from its queues to the clients. 
Immediately after failover, the new primary usually resends some messages that 
were already sent by the old primary. The client recognizes these as duplicates 
and discards them.
+
+In stage 1 of this figure, the primary sends an event message to the client 
and a synchronization message to its secondary. By stage 2, the secondary and 
client have updated their queue and message tracking information. If the 
primary failed at stage two, the secondary would start sending event messages 
from its queue beginning with message A10. The client would discard the resend 
of message A10 and then process subsequent messages as usual.
+
+
+## Change Server Queue Synchronization Frequency
+
+By default, the primary server sends queue synchronization messages to the 
secondaries every second. You can change this interval with the `gfsh alter 
runtime` command
+
+Set the interval for queue synchronization messages as follows:
+
+-   gfsh:
+
+``` pre
+gfsh>alter runtime --message-sync-interval=2
+```
+
+-   XML:
+
+``` pre
+ 
+
+```
+
+-   Java:
+
+``` pre
+cache = CacheFactory.create();
+cache.setMessageSyncInterval(2);  
+```
+
+The ideal setting for this interval depends in large part on your application 
behavior. These are the benefits of shorter and longer interval settings:
+
+-   A shorter interval requires less memory in the secondary servers because 
it reduces queue buildup between synchronizations. In addition, fewer old 
messages in the secondary queues means reduced message re-sends after a 
failover. These considerations are most important for systems with high data 
update rates.
+-   A longer interval requires fewer distribution messages between the primary 
and secondary, which benefits overall system performance.
+
+## Set Frequency of Orphan Removal from the Secondary 
Queues
+
+Usually, all event messages are removed from secondary subscription queues 
based on the primary's synchronization messages. Occasionally, however, some 
messages are orphaned in the secondary queues. For example, if a primary fails 
in the middle of sending a synchronization message to its secondaries, some 
secondaries might receive the message and some might not. If the failover goes 
to a secondary that did receive the message, the system will have secondary 
queues holding messages that are no longer in the primary queue. The new 
primary will never synchronize on these messages, leaving them orphaned 

[27/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb
--
diff --git 
a/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb 
b/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb
new file mode 100644
index 000..fb914be
--- /dev/null
+++ b/geode-docs/developing/transactions/how_cache_transactions_work.html.md.erb
@@ -0,0 +1,56 @@
+---
+title: How Geode Cache Transactions Work
+---
+
+
+
+This section provides an explanation of how transactions work on Geode caches.
+
+All the regions in a Geode member cache can participate in a transaction. A 
Java application can operate on the cache using multiple transactions. A 
transaction is associated with only one thread, and a thread can operate on 
only one transaction at a time. Child threads do not inherit existing 
transactions.
+
+-   **[Transaction 
View](../../developing/transactions/how_cache_transactions_work.html#concept_hls_1j1_wk)**
+
+-   **[Committing 
Transactions](../../developing/transactions/how_cache_transactions_work.html#concept_sbj_lj1_wk)**
+
+-   **[Transactions by Region 
Type](../../developing/transactions/cache_transactions_by_region_type.html#topic_nlq_sk1_wk)**
+
+-   **[Client 
Transactions](../../developing/transactions/client_server_transactions.html)**
+
+-   **[Comparing Transactional and Non-Transactional 
Operations](../../developing/transactions/transactional_and_nontransactional_ops.html#transactional_and_nontransactional_ops)**
+
+-   **[Geode Cache Transaction 
Semantics](../../developing/transactions/transaction_semantics.html)**
+
+## Transaction View
+
+A transaction is isolated from changes made concurrently to the cache. Each 
transaction has its own private view of the cache, including the entries it has 
read and the changes it has made. The first time the transaction touches an 
entry in the cache, either to read or write, it produces a snapshot of that 
entry’s state in the transaction’s view. The transaction maintains its 
current view of the entry, which reflects only the changes made within the 
transaction. The transaction remembers the entry’s original state and uses it 
at commit time to discover write conflicts.
+
+
+
+## Committing Transactions
+
+When a commit succeeds, the changes recorded in the transaction view are 
merged into the cache. If the commit fails or the transaction is rolled back, 
all of its changes are dropped.
+
+When a transaction is committed, the transaction management system uses a 
two-phase commit protocol:
+
+1.  Reserves all the entries involved in the transaction from changes by any 
other transactional thread. For distributed regions, it reserves the entries in 
the entire distributed system. For partitioned regions, it reserves them on the 
data store, where the transaction is running.
+2.  Checks the cache for conflicts on affected keys, to make sure all entries 
are still in the same state they were in when this transaction first accessed 
them.
+3.  If any conflict is detected, the manager rolls back the transaction.
+4.  If no conflict is detected, the manager:
+1.  Calls the `TransactionWriter` in the member where the transaction is 
running. This allows the system to write through transactional updates to an 
external data source.
+2.  Updates the local cache and distributes the updates to the other 
members holding the data. Cache listeners are called for these updates, in each 
cache where the changes are made, the same as for non-transactional operations.
+3.  Calls the `TransactionListener`s in the member where the transaction 
is running.
+
+5.  Releases the transaction reservations on the entries.
+
+The manager updates the local cache and distributes the updates to other 
members in a non-atomic way.
+
+-   If other threads read the keys the transaction is modifying, they may see 
some in their pre-transaction state and some in their post-transaction state.
+-   If other, non-transactional sources update the keys the transaction is 
modifying, the changes may intermingle with this transaction’s changes. The 
other sources can include distributions from remote members, loading 
activities, and other direct cache modification calls from the same member. 
When this happens, after your commit finishes, the cache state may not be what 
you expected.
+
+If the transaction fails to complete any of the steps, a 
CommitConflictException is thrown to the calling application.
+
+Once the members involved in the transaction have been asked to commit, the 
transaction completes even if one of the participating members were to leave 
the system during the commit. The transaction completes successfully so long as 
all remaining members are in agreement.
+
+Each member participating in the transaction maintains a membership listener 
on the transaction 

[28/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/region_options/region_types.html.md.erb
--
diff --git a/geode-docs/developing/region_options/region_types.html.md.erb 
b/geode-docs/developing/region_options/region_types.html.md.erb
new file mode 100644
index 000..45908dd
--- /dev/null
+++ b/geode-docs/developing/region_options/region_types.html.md.erb
@@ -0,0 +1,129 @@
+---
+title:  Region Types
+---
+
+Region types define region behavior within a single distributed system. You 
have various options for region data storage and distribution.
+
+
+Within a Geode distributed system, you can define distributed regions and 
non-distributed regions, and you can define regions whose data is spread across 
the distributed system, and regions whose data is entirely contained in a 
single member.
+
+Your choice of region type is governed in part by the type of application you 
are running. In particular, you need to use specific region types for your 
servers and clients for effective communication between the two tiers:
+
+-   Server regions are created inside a `Cache` by servers and are accessed by 
clients that connect to the servers from outside the server's distributed 
system. Server regions must have region type partitioned or replicated. Server 
region configuration uses the `RegionShortcut` enum settings.
+-   Client regions are created inside a `ClientCache` by clients and are 
configured to distribute data and events between the client and the server 
tier. Client regions must have region type `local`. Client region configuration 
uses the `ClientRegionShortcut` enum settings.
+-   Peer regions are created inside a `Cache`. Peer regions may be server 
regions, or they may be regions that are not accessed by clients. Peer regions 
can have any region type. Peer region configuration uses the `RegionShortcut` 
enum settings.
+
+When you configure a server or peer region using `gfsh` or with the 
`cache.xml` file, you can use *region shortcuts* to define the basic 
configuration of your region. A region shortcut provides a set of default 
configuration attributes that are designed for various types of caching 
architectures. You can then add additional configuration attributes as needed 
to customize your application. For more information and a complete reference of 
these region shortcuts, see [Region Shortcuts 
Reference](../../reference/topics/region_shortcuts_reference.html#reference_lt4_54c_lk).
+
+
+
+These are the primary configuration choices for each data region.
+
+
+
+
+
+
+
+
+
+Region Type
+Description
+Best suited for...
+
+
+
+
+Partitioned
+System-wide setting for the data set. Data is divided into buckets across 
the members that define the region. For high availability, configure redundant 
copies so each bucket is stored in multiple members with one member holding the 
primary.
+Server regions and peer regions
+
+Very large data sets
+High availability
+Write performance
+Partitioned event listeners and data loaders
+
+
+
+Replicated (distributed)
+Holds all data from the distributed region. The data from the distributed 
region is copied into the member replica region. Can be mixed with 
non-replication, with some members holding replicas and some holding 
non-replicas.
+Server regions and peer regions
+
+Read heavy, small datasets
+Asynchronous distribution
+Query performance
+
+
+
+Distributed non-replicated
+Data is spread across the members that define the region. Each member 
holds only the data it has expressed interest in. Can be mixed with 
replication, with some members holding replicas and some holding 
non-replicas.
+Peer regions, but not server regions and not client regions
+
+Asynchronous distribution
+Query performance
+
+
+
+Non-distributed (local)
+The region is visible only to the defining member.
+Client regions and peer regions
+
+Data that is not shared between applications
+
+
+
+
+
+## Partitioned Regions
+
+Partitioning is a good choice for very large server regions. Partitioned 
regions are ideal for data sets in the hundreds of gigabytes and beyond.
+
+**Note:**
+Partitioned regions generally require more JDBC connections than other region 
types because each member that hosts data must have a connection.
+
+Partitioned regions group your data into buckets, each of which is stored on a 
subset of all of the system members. Data location in the buckets does not 
affect the logical view - all members see the same logical data set.
+
+Use partitioning for:
+
+-   **Large data sets**. Store data sets that are too large to fit into a 
single member, and all members will see the same logical data set. Partitioned 
regions divide the data into units of storage called buckets that are split 
across the members hosting the partitioned region data, so no member needs to 
host all of the region’s data. Geode provides dynamic redundancy recovery and 

[43/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/outside_data_sources/sync_outside_data.html.md.erb
--
diff --git a/developing/outside_data_sources/sync_outside_data.html.md.erb 
b/developing/outside_data_sources/sync_outside_data.html.md.erb
deleted file mode 100644
index 54e4f48..000
--- a/developing/outside_data_sources/sync_outside_data.html.md.erb
+++ /dev/null
@@ -1,19 +0,0 @@

-title:  Keeping the Cache in Sync with Outside Data Sources

-
-Keep your distributed cache in sync with an outside data source by programming 
and installing application plug-ins for your region.
-
--   **[Overview of Outside Data 
Sources](../../developing/outside_data_sources/chapter_overview.html)**
-
-Apache Geode has application plug-ins to read data into the cache and 
write it out.
-
--   **[How Data Loaders 
Work](../../developing/outside_data_sources/how_data_loaders_work.html)**
-
-By default, a region has no data loader defined. Plug an 
application-defined loader into any region by setting the region attribute 
cache-loader on the members that host data for the region.
-
--   **[Implement a Data 
Loader](../../developing/outside_data_sources/implementing_data_loaders.html)**
-
-Program a data loader and configure your region to use it.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/partitioned_regions/chapter_overview.html.md.erb
--
diff --git a/developing/partitioned_regions/chapter_overview.html.md.erb 
b/developing/partitioned_regions/chapter_overview.html.md.erb
deleted file mode 100644
index 56e65e1..000
--- a/developing/partitioned_regions/chapter_overview.html.md.erb
+++ /dev/null
@@ -1,43 +0,0 @@

-title:  Partitioned Regions

-
-In addition to basic region management, partitioned regions include options 
for high availability, data location control, and data balancing across the 
distributed system.
-
--   **[Understanding 
Partitioning](../../developing/partitioned_regions/how_partitioning_works.html)**
-
-To use partitioned regions, you should understand how they work and your 
options for managing them.
-
--   **[Configuring Partitioned 
Regions](../../developing/partitioned_regions/managing_partitioned_regions.html)**
-
-Plan the configuration and ongoing management of your partitioned region 
for host and accessor members and configure the regions for startup.
-
--   **[Configuring the Number of Buckets for a Partitioned 
Region](../../developing/partitioned_regions/configuring_bucket_for_pr.html)**
-
-Decide how many buckets to assign to your partitioned region and set the 
configuration accordingly.
-
--   **[Custom-Partitioning and Colocating 
Data](../../developing/partitioned_regions/overview_custom_partitioning_and_data_colocation.html)**
-
-You can customize how Apache Geode groups your partitioned region data 
with custom partitioning and data colocation.
-
--   **[Configuring High Availability for Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_ha_works.html)**
-
-By default, Apache Geode stores only a single copy of your partitioned 
region data among the region's data stores. You can configure Geode to maintain 
redundant copies of your partitioned region data for high availability.
-
--   **[Configuring Single-Hop Client Access to Server-Partitioned 
Regions](../../developing/partitioned_regions/overview_how_pr_single_hop_works.html)**
-
-Single-hop data access enables the client pool to track where a 
partitioned region’s data is hosted in the servers. To access a single entry, 
the client directly contacts the server that hosts the key, in a single hop.
-
--   **[Rebalancing Partitioned Region 
Data](../../developing/partitioned_regions/rebalancing_pr_data.html)**
-
-In a distributed system with minimal contention to the concurrent threads 
reading or updating from the members, you can use rebalancing to dynamically 
increase or decrease your data and processing capacity.
-
--   **[Checking Redundancy in Partitioned 
Regions](../../developing/partitioned_regions/checking_region_redundancy.html)**
-
-Under some circumstances, it can be important to verify that your 
partitioned region data is redundant and that upon member restart, redundancy 
has been recovered properly across partitioned region members.
-
--   **[Moving Partitioned Region Data to Another 
Member](../../developing/partitioned_regions/moving_partitioned_data.html)**
-
-You can use the `PartitionRegionHelper` `moveBucketByKey` and `moveData` 
methods to explicitly move partitioned region data from one member to another.
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/partitioned_regions/checking_region_redundancy.html.md.erb

[40/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/region_options/region_types.html.md.erb
--
diff --git a/developing/region_options/region_types.html.md.erb 
b/developing/region_options/region_types.html.md.erb
deleted file mode 100644
index 45908dd..000
--- a/developing/region_options/region_types.html.md.erb
+++ /dev/null
@@ -1,129 +0,0 @@

-title:  Region Types

-
-Region types define region behavior within a single distributed system. You 
have various options for region data storage and distribution.
-
-
-Within a Geode distributed system, you can define distributed regions and 
non-distributed regions, and you can define regions whose data is spread across 
the distributed system, and regions whose data is entirely contained in a 
single member.
-
-Your choice of region type is governed in part by the type of application you 
are running. In particular, you need to use specific region types for your 
servers and clients for effective communication between the two tiers:
-
--   Server regions are created inside a `Cache` by servers and are accessed by 
clients that connect to the servers from outside the server's distributed 
system. Server regions must have region type partitioned or replicated. Server 
region configuration uses the `RegionShortcut` enum settings.
--   Client regions are created inside a `ClientCache` by clients and are 
configured to distribute data and events between the client and the server 
tier. Client regions must have region type `local`. Client region configuration 
uses the `ClientRegionShortcut` enum settings.
--   Peer regions are created inside a `Cache`. Peer regions may be server 
regions, or they may be regions that are not accessed by clients. Peer regions 
can have any region type. Peer region configuration uses the `RegionShortcut` 
enum settings.
-
-When you configure a server or peer region using `gfsh` or with the 
`cache.xml` file, you can use *region shortcuts* to define the basic 
configuration of your region. A region shortcut provides a set of default 
configuration attributes that are designed for various types of caching 
architectures. You can then add additional configuration attributes as needed 
to customize your application. For more information and a complete reference of 
these region shortcuts, see [Region Shortcuts 
Reference](../../reference/topics/region_shortcuts_reference.html#reference_lt4_54c_lk).
-
-
-
-These are the primary configuration choices for each data region.
-
-
-
-
-
-
-
-
-
-Region Type
-Description
-Best suited for...
-
-
-
-
-Partitioned
-System-wide setting for the data set. Data is divided into buckets across 
the members that define the region. For high availability, configure redundant 
copies so each bucket is stored in multiple members with one member holding the 
primary.
-Server regions and peer regions
-
-Very large data sets
-High availability
-Write performance
-Partitioned event listeners and data loaders
-
-
-
-Replicated (distributed)
-Holds all data from the distributed region. The data from the distributed 
region is copied into the member replica region. Can be mixed with 
non-replication, with some members holding replicas and some holding 
non-replicas.
-Server regions and peer regions
-
-Read heavy, small datasets
-Asynchronous distribution
-Query performance
-
-
-
-Distributed non-replicated
-Data is spread across the members that define the region. Each member 
holds only the data it has expressed interest in. Can be mixed with 
replication, with some members holding replicas and some holding 
non-replicas.
-Peer regions, but not server regions and not client regions
-
-Asynchronous distribution
-Query performance
-
-
-
-Non-distributed (local)
-The region is visible only to the defining member.
-Client regions and peer regions
-
-Data that is not shared between applications
-
-
-
-
-
-## Partitioned Regions
-
-Partitioning is a good choice for very large server regions. Partitioned 
regions are ideal for data sets in the hundreds of gigabytes and beyond.
-
-**Note:**
-Partitioned regions generally require more JDBC connections than other region 
types because each member that hosts data must have a connection.
-
-Partitioned regions group your data into buckets, each of which is stored on a 
subset of all of the system members. Data location in the buckets does not 
affect the logical view - all members see the same logical data set.
-
-Use partitioning for:
-
--   **Large data sets**. Store data sets that are too large to fit into a 
single member, and all members will see the same logical data set. Partitioned 
regions divide the data into units of storage called buckets that are split 
across the members hosting the partitioned region data, so no member needs to 
host all of the region’s data. Geode provides dynamic redundancy recovery and 
rebalancing of partitioned regions, making them 

[39/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/transactions/jca_adapter_example.html.md.erb
--
diff --git a/developing/transactions/jca_adapter_example.html.md.erb 
b/developing/transactions/jca_adapter_example.html.md.erb
deleted file mode 100644
index 1e562cd..000
--- a/developing/transactions/jca_adapter_example.html.md.erb
+++ /dev/null
@@ -1,34 +0,0 @@

-title:  JCA Resource Adapter Example

-
-This example shows how to use the JCA Resource Adapter in Geode .
-
-``` pre
-Hashtable env = new Hashtable();
-env.put(Context.INITIAL_CONTEXT_FACTORY, 
“weblogic.jndi.WLInitialContextFactory”);
-env.put(Context.PROVIDER_URL, “t3://localhost:7001”);
-Context ctx = new InitialContext(env);
-UserTransaction utx = (UserTransaction) 
ctx.lookup(“javax.transaction.UserTransaction”);
-utx.begin();
-  // the XA Resource
-javax.sql.DataSource ds = (DataSource) ctx.lookup(“derby”);
-javax.sql.Connection derbyConn = ds.getConnection();
-Statement stmt = conn.createStatement();
-stmt.executeUpdate(“insert into test values(2,4) “);
- // do ConnectionFactory lookup
-GFConnectionFactory cf = (GFConnectionFactory) ctx.lookup(“gfe/jca”);
-
- // Obtaining the connection begins the LocalTransaction.
- // If this is absent, operations will not be part of any transaction.
-GFConnection conn = cf.getConnection();
-
-testRegion.put(“foo”, “bar-”);
-utx.commit();
-
- // the connection can also be closed within the transaction
-derbyConn.close();
-conn.close();
-```
-
-

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/transactions/monitor_troubleshoot_transactions.html.md.erb
--
diff --git 
a/developing/transactions/monitor_troubleshoot_transactions.html.md.erb 
b/developing/transactions/monitor_troubleshoot_transactions.html.md.erb
deleted file mode 100644
index 6cb1b6c..000
--- a/developing/transactions/monitor_troubleshoot_transactions.html.md.erb
+++ /dev/null
@@ -1,39 +0,0 @@

-title:  Monitoring and Troubleshooting Transactions

-
-This topic covers errors that may occur when running transactions in Geode.
-
-
-Unlike database transactions, Geode does not write a transaction log to disk. 
To get the full details about committed operations, use a transaction listener 
to monitor the transaction events and their contained cache events for each of 
your transactions.
-
-## Statistics on Cache Transactions
-
-During the operation of Geode cache transactions, if statistics are enabled, 
transaction-related statistics are calculated and accessible from the 
CachePerfStats statistic resource. Because the transaction’s data scope is 
the cache, these statistics are collected on a per-cache basis.
-
-## Commit
-
-In a failed commit, the exception lists the first conflict that caused the 
failure. Other conflicts can exist, but are not reported.
-
-## Capacity Limits
-
-A transaction can create data beyond the capacity limit set in the region’s 
eviction attributes. The capacity limit does not take effect until commit time. 
Then, any required eviction action takes place as part of the commit.
-
-## Interaction with the Resource Manager
-
-The Geode resource manager, which controls overall heap use, either allows all 
transactional operations or blocks the entire transaction. If a cache reaches 
the critical threshold in the middle of a commit, the commit is allowed to 
finish before the manager starts blocking operations.
-
-## Transaction Exceptions
-
-The following sections list possible transaction exceptions.
-
-**Exceptions Indicating Transaction Failure**
-
--   **`TransactionDataNodeHasDepartedException`**. This exception means the 
transaction host has departed unexpectedly. Clients and members that run 
transactions but are not a transaction host can get this exception. You can 
avoid this by working to ensure your transaction hosts are stable and remain 
running when transactions are in progress.
--   **`TransactionDataNotColocatedException`**. You will get this error if you 
try to run a transaction on data that is not all located in the same member. 
Partition your data so that a single member contains all data that will be 
accessed as part of a single transaction. See [Transactions and Partitioned 
Regions](cache_transactions_by_region_type.html#concept_ysk_xj1_wk) and 
[Understanding Custom Partitioning and Data 
Colocation](../partitioned_regions/custom_partitioning_and_data_colocation.html#custom_partitioning_and_data_colocation).
--   **`TransactionDataRebalancedException`**. You get this error if your 
transactional data is moved to another member for rebalancing during the 
transaction. Manage your partitioned region data to avoid rebalancing during a 
transaction. See [Rebalancing Partitioned Region 

[11/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_local_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_local_1.svg 
b/geode-docs/images_svg/transactions_replicate_local_1.svg
new file mode 100644
index 000..47bb4e7
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_local_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="41 158 319 301" 
width="319pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:04Zreplicate-localLayer 
1MemberCacheReplicate Region AJava ApplicationXT1YZRegion AX1Y1Region AY2Z2T2Transaction T1Transaction T2

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_no_ack_1.svg 
b/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
new file mode 100644
index 000..1d94d72
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_no_ack_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="133 203 584 337" 
width="584pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:00Zreplicate-no-ack-1Layer 
1W1X1X2Member (M1)CacheReplicate Region AJava ApplicationWMember 
(M2)Replicate Region 
BXRegion AW1Region 
BX1Transaction T1CacheReplicate Region 
AWMember (M3)CacheReplicate Region 
BX2Replicate Region 
BXTransaction T2Java Application

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
--
diff --git a/geode-docs/images_svg/transactions_replicate_no_ack_2.svg 
b/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
new file mode 100644
index 000..8b4d41a
--- /dev/null
+++ b/geode-docs/images_svg/transactions_replicate_no_ack_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="19 148 584 337" 
width="584pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:02Zreplicate-no-ack-2Layer 
1Member (M1)CacheReplicate Region AJava ApplicationW1Member (M2)Replicate Region 
B
 X2CacheReplicate Region AW1Member 
(M3)CacheReplicate Region 
BX1Java Application

[08/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/heap_use/off_heap_management.html.md.erb
--
diff --git a/geode-docs/managing/heap_use/off_heap_management.html.md.erb 
b/geode-docs/managing/heap_use/off_heap_management.html.md.erb
new file mode 100644
index 000..0c8bf7c
--- /dev/null
+++ b/geode-docs/managing/heap_use/off_heap_management.html.md.erb
@@ -0,0 +1,192 @@
+---
+title: Managing Off-Heap Memory
+---
+
+
+
+Geode can be configured to store region values in off-heap memory, which is 
memory within the JVM that is not subject to Java garbage collection.
+
+Garbage collection (GC) within a JVM can prove to be a performance impediment. 
A server cannot exert control over when garbage collection within the JVM heap 
memory takes place, and the server has little control over the triggers for 
invocation. Off-heap memory offloads values to a storage area that is not 
subject to Java GC. By taking advantage of off-heap storage, an application can 
reduce the amount of heap storage that is subject to GC overhead.
+
+Off-heap memory works in conjunction with the heap, it does not replace it. 
The keys are stored in heap memory space. Geode's own memory manager handles 
the off-heap memory with better performance than the Java garbage collector 
would for certain sets of region data.
+
+The resource manager monitors the contents of off-heap memory and invokes 
memory management operations in accordance with two thresholds similar to those 
used for monitoring the JVM heap: `eviction-off-heap-percentage` and 
`critical-off-heap-percentage`.
+
+## On-heap and Off-heap Objects
+
+The following objects are always stored in the JVM heap:
+
+-   Region metadata
+-   Entry metadata
+-   Keys
+-   Indexes
+-   Subscription queue elements
+
+The following objects can be stored in off-heap memory:
+
+-   Values - maximum value size is 2GB
+-   Reference counts
+-   List of free memory blocks
+-   WAN queue elements
+
+**Note:**
+Do not use functional range indexes with off-heap data, as they are not 
supported. An attempt to do so generates an exception.
+
+## Off-heap Recommendations
+
+Off-heap storage is best suited to data patterns where:
+
+-   Stored values are relatively uniform in size
+-   Stored values are mostly less than 128K in size
+-   The usage patterns involve cycles of many creates followed by destroys or 
clear
+-   The values do not need to be frequently deserialized
+-   Many of the values are long-lived reference data
+
+Be aware that Geode has to perform extra work to access the data stored in 
off-heap memory since it is stored in serialized form. This extra work may 
cause some use cases to run slower in an off-heap configuration, even though 
they use less memory and avoid garbage collection overhead. However, even with 
the extra deserialization, off-heap storage may give you the best performance. 
Features that may increase overhead include
+
+-   frequent updates
+-   stored values of widely varying sizes
+-   deltas
+-   queries
+
+## Implementation Details
+
+The off-heap memory manager is efficient at handling region data values that 
are all the same size or are of fixed sizes. With fixed and same-sized data 
values allocated within the off-heap memory, freed chunks can often be re-used, 
and there is little or no need to devote cycles to defragmentation.
+
+Region values that are less than or equal to eight bytes in size will not 
reside in off-heap memory, even if the region is configured to use off-heap 
memory. These very small size region values reside in the JVM heap in place of 
a reference to an off-heap location. This performance enhancement saves space 
and load time.
+
+## Controlling Off-heap Use with the Resource Manager
+
+The Geode resource manager controls off-heap memory by means of two 
thresholds, in much the same way as it does JVM heap memory. See [Using the 
Geode Resource Manager](heap_management.html#how_the_resource_manager_works). 
The resource manager prevents the cache from consuming too much off-heap memory 
by evicting old data. If the off-heap memory manager is unable to keep up, the 
resource manager refuses additions to the cache until the off-heap memory 
manager has freed an adequate amount of memory.
+
+The resource manager has two threshold settings, each expressed as a 
percentage of the total off-heap memory. Both are disabled by default.
+
+1.  **Eviction Threshold**. The percentage of off-heap memory at which 
eviction should begin. Evictions continue until the resource manager determines 
that off-heap memory use is again below the eviction threshold. Set the 
eviction threshold with the `eviction-off-heap-percentage` region attribute. 
The resource manager enforces an eviction threshold only on regions with the 
HEAP\_LRU characteristic. If critical threshold is non-zero, the default 
eviction threshold is 5% below the critical 

[25/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/JMX_Architecture.svg
--
diff --git a/geode-docs/images_svg/JMX_Architecture.svg 
b/geode-docs/images_svg/JMX_Architecture.svg
new file mode 100644
index 000..f60c097
--- /dev/null
+++ b/geode-docs/images_svg/JMX_Architecture.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="106 331 380 360" 
width="380pt" height="30pc" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 00:09Zjmx 
architectureLayer 1Management and 
Monitoring ToolsJMX Manager Node Distributed SystemOther JMX Clients (JConsole, jvisualvm)
 Managed NodeManaged NodeCMBean ServerDAMBean ServerBMBean ServerY+XAManagerMBeanx="1.9985352" y="9" textLength="6.0029297">Btransform="translate(139 442.875)" fill="black">font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x=".75927734" y="6" textLength="45.023438">Proxied Mbeans font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x="3.0942383" y="13" textLength="40.353516">from Managed font-family="Helvetica" font-size="6" font-weight="500" fill="black" 
 >x="13.765625" y="20" textLength="17.34375">Nodesmarker-end="url(#FilledArrow_Marker_2)" stroke="black" stroke-linecap="round" 
 >stroke-linejoin="round" stroke-width=".23998"/>d="M 159.66 546.75 L 245.34 546.75 C 249.01822 546.75 252 549.73178 252 
 >553.41 L 252 558.09 C 252 5
 61.7682 249.01822 564.75 245.34 564.75 L 159.66 564.75 C 155.98178 564.75 153 
561.7682 153 558.09 L 153 553.41 C 153 549.73178 155.98178 546.75 159.66 546.75 
Z" fill="url(#Obj_Gradient_c)"/>Management ServiceManagement 
ServiceRMI 
ConnectorManagement ServiceCDgfshMemberMBeanMemberMBeanLocal 
MBeansLocal 
MBeansLocal MBeansZYAggregate MBeanMemberMBeanPulseOther JMX Clients (JConsole, jvisualvm)Local view of 
managed node 
onlyRMI 
ConnectorView of 
remote managed node

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/MBeans.svg
--
diff --git a/geode-docs/images_svg/MBeans.svg b/geode-docs/images_svg/MBeans.svg
new file mode 100644
index 000..cdfcf6e
--- /dev/null
+++ b/geode-docs/images_svg/MBeans.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="54 72 504 450" 
width="42pc" height="450pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 23:57ZmbeanLayer 1DistributedLockServiceMXBeanLocatorMXBeanMemberMXBeanManagerMXBeanDistributedRegionMXBeanDistributedSystemMXBeanJMX Manager NodeRegionMXBeanLockServiceMXBeanManaged NodeDiskStoreMXBean110..N0..10..N10..N0..N0..NAsyncEventQueueMXBeanCacheServerMXBean10..N

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/async_system_queue_conflation.svg
--
diff --git a/geode-docs/images_svg/async_system_queue_conflation.svg 
b/geode-docs/images_svg/async_system_queue_conflation.svg
new file mode 100644
index 000..fcc8635
--- /dev/null
+++ b/geode-docs/images_svg/async_system_queue_conflation.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="61 349 454 346" 
width="454pt" height="346pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 08:59ZconflationLayer 1Initial producer queue 
w
 ith conflationentry createKey Bentry updateKey AValue QV1to consumerentry updateKey AValue V2Add entry update to 
queue...entry 
createKey 
Bentry updateKey AValue 
V1to consumerQueue after conflationentry updateKey AValue 
V2entry 
createKey 
Bto consumer

[30/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_additional/case_sensitivity.html.md.erb
--
diff --git 
a/geode-docs/developing/query_additional/case_sensitivity.html.md.erb 
b/geode-docs/developing/query_additional/case_sensitivity.html.md.erb
new file mode 100644
index 000..2d49259
--- /dev/null
+++ b/geode-docs/developing/query_additional/case_sensitivity.html.md.erb
@@ -0,0 +1,19 @@
+---
+title:  Case Sensitivity
+---
+
+Query language keywords such as SELECT, NULL, DATE, and TRACE are 
case-insensitive. Identifiers such as attribute names, method names, and path 
expressions are case-sensitive.
+
+In terms of query string and region entry matching, if you want to perform a 
case-insensitive search on a particular field, you can use the Java String 
class `toUpperCase` and `toLowerCase` methods in your query. For example:
+
+``` pre
+SELECT entry.value FROM /exampleRegion.entries entry WHERE 
entry.value.toUpperCase LIKE '%BAR%'
+```
+
+or
+
+``` pre
+SELECT * FROM /exampleRegion WHERE foo.toLowerCase LIKE '%bar%'
+```
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/developing/query_additional/literals.html.md.erb
--
diff --git a/geode-docs/developing/query_additional/literals.html.md.erb 
b/geode-docs/developing/query_additional/literals.html.md.erb
new file mode 100644
index 000..37fcc0f
--- /dev/null
+++ b/geode-docs/developing/query_additional/literals.html.md.erb
@@ -0,0 +1,65 @@
+---
+title:  Supported Literals
+---
+
+## Comparing Values With java.util.Date
+
+Geode supports the following literal types:
+
+**boolean**
+A `boolean` value, either TRUE or FALSE
+**int** and **long**
+An integer literal is of type `long` if has a suffix of the ASCII letter 
L. Otherwise it is of type `int`.
+**floating point**
+A floating-point literal is of type `float` if it has a suffix of an ASCII 
letter `F`. Otherwise its type is `double`. Optionally, it can have a suffix of 
an ASCII letter `D`. A double or floating point literal can optionally include 
an exponent suffix of `E` or `e`, followed by a signed or unsigned number.
+
+**string**
+String literals are delimited by single quotation marks. Embedded 
single-quotation marks are doubled. For example, the character string `'Hello'` 
evaluates to the value `Hello`, while the character string `'He said, 
''Hello'''` evaluates to `He said, 'Hello'`. Embedded newlines are kept as part 
of the string literal.
+**char**
+A literal is of type char if it is a string literal prefixed by the 
keyword `CHAR`, otherwise it is of type `string`. The `CHAR` literal for the 
single-quotation mark character is `CHAR` `` (four single quotation 
marks).
+**date**
+A `java.sql.Date` object that uses the JDBC format prefixed with the DATE 
keyword: `DATE -mm-dd`. In the `Date`, `` represents the year, `mm` 
represents the month, and `dd` represents the day. The year must be represented 
by four digits; a two-digit shorthand for the year is not allowed.
+**time**
+A `java.sql.Time` object that uses the JDBC format (based on a 24-hour 
clock) prefixed with the TIME keyword: `TIME hh:mm:ss`. In the `Time`, `hh` 
represents the hours, `mm` represents the minutes, and `ss` represents the 
seconds.
+**timestamp**
+A `java.sql.Timestamp` object that uses the JDBC format with a TIMESTAMP 
prefix: `TIMESTAMP -mm-dd hh:mm:ss.f` In the `Timestamp`, 
`-mm-dd` represents the `date`, `hh:mm:ss` represents the `time`, and 
`f` represents the fractional seconds (up to nine digits).
+**NIL**
+Equivalent alternative of `NULL`.
+**NULL**
+The same as `null` in Java.
+**UNDEFINED**
+A special literal that is a valid value for any data type. An `UNDEFINED` 
value is the result of accessing an attribute of a null-valued attribute. Note 
that if you access an attribute that has an explicit value of null, then it is 
not undefined. For example if a query accesses the attribute address.city and 
address is null, the result is undefined. If the query accesses address, then 
the result is not undefined, it is `NULL`.
+
+You can compare temporal literal values `DATE`, `TIME`, and `TIMESTAMP` with 
`java.util.Date` values. There is no literal for `java.util.Date` in the query 
language.
+
+## Type Conversion
+
+The Geode query processor performs implicit type conversions and promotions 
under certain cases in order to evaluate expressions that contain different 
types. The query processor performs binary numeric promotion, method invocation 
conversion, and temporal type conversion.
+
+## Binary Numeric Promotion
+
+The query processor performs binary numeric promotion on the operands of the 
following operators:
+
+-   Comparison operators , =, , and =
+-   Equality operators = and 
+-   Binary numeric promotion widens the operands in a 

[51/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

GEODE-1952 Consolidated docs under a single geode-docs directory


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

Branch: refs/heads/feature/GEODE-1952
Commit: ccc2fbda4001884a0bf36ca2d76d75358cbda3eb
Parents: 2eabdb2
Author: Dave Barnes 
Authored: Tue Oct 4 10:32:02 2016 -0700
Committer: Dave Barnes 
Committed: Tue Oct 4 10:32:02 2016 -0700

--
 .gitignore  |6 -
 CONTRIBUTE.md   |   63 -
 README.md   |   93 -
 about_geode.html.md.erb |9 -
 basic_config/book_intro.html.md.erb |   23 -
 .../chapter_overview.html.md.erb|   23 -
 ...uted_system_member_configuration.html.md.erb |   34 -
 .../config_concepts/local_vs_remote.html.md.erb |   12 -
 .../chapter_overview.html.md.erb|   15 -
 .../managing_data_entries.html.md.erb   |  129 -
 .../using_custom_classes.html.md.erb|   34 -
 .../data_regions/chapter_overview.html.md.erb   |   48 -
 .../create_a_region_with_API.html.md.erb|   63 -
 .../create_a_region_with_cacheXML.html.md.erb   |   68 -
 .../create_a_region_with_gfsh.html.md.erb   |   38 -
 .../creating_custom_attributes.html.md.erb  |   47 -
 .../managing_data_regions.html.md.erb   |  205 --
 .../managing_region_attributes.html.md.erb  |   96 -
 .../new_region_existing_data.html.md.erb|   11 -
 .../data_regions/region_naming.html.md.erb  |   14 -
 .../data_regions/region_shortcuts.html.md.erb   |   98 -
 .../store_retrieve_region_shortcuts.html.md.erb |   60 -
 .../setting_distributed_properties.html.md.erb  |   64 -
 .../the_cache/chapter_overview.html.md.erb  |   31 -
 .../intro_cache_management.html.md.erb  |   79 -
 .../managing_a_client_cache.html.md.erb |   67 -
 .../managing_a_multiuser_cache.html.md.erb  |   49 -
 .../managing_a_peer_server_cache.html.md.erb|   64 -
 .../managing_a_secure_cache.html.md.erb |   50 -
 .../setting_cache_initializer.html.md.erb   |   59 -
 .../setting_cache_properties.html.md.erb|   22 -
 configuring/chapter_overview.html.md.erb|   67 -
 .../deploying_application_jars.html.md.erb  |  114 -
 .../cluster_config/export-import.html.md.erb|   39 -
 .../gfsh_config_troubleshooting.html.md.erb |   58 -
 .../gfsh_load_from_shared_dir.html.md.erb   |   27 -
 .../cluster_config/gfsh_persist.html.md.erb |  108 -
 .../cluster_config/gfsh_remote.html.md.erb  |   61 -
 .../persisting_configurations.html.md.erb   |  320 --
 .../using_member_groups.html.md.erb |   27 -
 .../running/change_file_spec.html.md.erb|   40 -
 .../running/default_file_specs.html.md.erb  |   59 -
 .../deploy_config_files_intro.html.md.erb   |   17 -
 .../running/deploying_config_files.html.md.erb  |   28 -
 .../deploying_config_jar_files.html.md.erb  |   35 -
 .../running/firewall_ports_config.html.md.erb   |   15 -
 .../running/firewalls_connections.html.md.erb   |   18 -
 .../running/firewalls_multisite.html.md.erb |   70 -
 configuring/running/firewalls_ports.html.md.erb |  229 --
 .../running/managing_output_files.html.md.erb   |   16 -
 .../running/running_the_cacheserver.html.md.erb |  182 -
 .../running/running_the_locator.html.md.erb |  240 --
 .../starting_up_shutting_down.html.md.erb   |  129 -
 developing/book_intro.html.md.erb   |   57 -
 .../chapter_overview.html.md.erb|   21 -
 .../continuous_querying_whats_next.html.md.erb  |   71 -
 .../how_continuous_querying_works.html.md.erb   |   81 -
 ...implementing_continuous_querying.html.md.erb |  185 -
 .../PDX_Serialization_Features.html.md.erb  |   23 -
 .../auto_serialization.html.md.erb  |  124 -
 ...ation_with_class_pattern_strings.html.md.erb |   68 -
 .../chapter_overview.html.md.erb|   23 -
 .../data_serialization_options.html.md.erb  |   51 -
 .../extending_the_autoserializer.html.md.erb|  106 -
 .../gemfire_data_serialization.html.md.erb  |   35 -
 .../gemfire_pdx_serialization.html.md.erb   |   47 -
 .../java_serialization.html.md.erb  |   12 -
 .../jsonformatter_pdxinstances.html.md.erb  |   29 -
 .../persist_pdx_metadata_to_disk.html.md.erb|   36 -
 .../program_application_for_pdx.html.md.erb |   90 -
 .../use_pdx_high_level_steps.html.md.erb|   32 -
 .../use_pdx_serializable.html.md.erb|   98 -
 .../use_pdx_serializer.html.md.erb  |  128 -
 .../using_PdxInstanceFactory.html.md.erb|   

[15/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/region_entry_versions_2.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_2.svg 
b/geode-docs/images_svg/region_entry_versions_2.svg
new file mode 100644
index 000..0efcc23
--- /dev/null
+++ b/geode-docs/images_svg/region_entry_versions_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="17 33 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-03 01:12ZCanvas 9Layer 1Member C
 Replicated 
RegionMember 
AMember 
BApplicationReplicated 
RegionX 
(A3)Replicated RegionApplicationApplicationX 
(A3)X 
(C3)X (A3)X 
(A3)(ignored)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/region_entry_versions_3.svg
--
diff --git a/geode-docs/images_svg/region_entry_versions_3.svg 
b/geode-docs/images_svg/region_entry_versions_3.svg
new file mode 100644
index 000..105db57
--- /dev/null
+++ b/geode-docs/images_svg/region_entry_versions_3.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="26 101 535 193" 
width="535pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-03 01:12ZCanvas 8Layer 1Member CReplicated RegionMember A 
Member BApplicationReplicated RegionX (C3)Replicated 
RegionApplicationApplicationX (C3)X (C3)X 
(C3)X 
(C3)

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/server_client_event_dist.svg
--
diff --git a/geode-docs/images_svg/server_client_event_dist.svg 
b/geode-docs/images_svg/server_client_event_dist.svg
new file mode 100644
index 000..2d726cd
--- /dev/null
+++ b/geode-docs/images_svg/server_client_event_dist.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="27 275 293 301" 
width="293pt" height="301pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:51Z
 cs-event-distributionLayer 
1Client 
1Region Apool-name = ServerPoolinterest in XreceiveValues = trueServerRegion AXCache 
ServerClient 2XUpdate/CreateRegion Apool-name = ServerPoolinterest in XreceiveValues = 
falsepool 
“ServerPool”(with 
subscriptions enabled)pool 
“ServerPool”(with 
subscriptions enabled)Update/CreateInvalidateXX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/server_discovery.svg
--
diff --git a/geode-docs/images_svg/server_discovery.svg 
b/geode-docs/images_svg/server_discovery.svg
new file mode 100644
index 000..661b66f
--- /dev/null
+++ b/geode-docs/images_svg/server_discovery.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="176 248 373 341" 
width="373pt" height="341pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:31Zhow_server_discovery_worksLayer 
1Server #1ClientLocal Cacheconnection poolLocatorsend address and load inforequest serverconnectionServer 
#2Cache DataCache Datalistening on 10.80.100.1 :  
40404listening on 10.80.100.2 :  40404listening on lucy : 4locator atlucy : 41use 
10.80.100.2 : 404042client/server communication3

[46/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/developing/delta_propagation/implementing_delta_propagation.html.md.erb
--
diff --git 
a/developing/delta_propagation/implementing_delta_propagation.html.md.erb 
b/developing/delta_propagation/implementing_delta_propagation.html.md.erb
deleted file mode 100644
index 7727532..000
--- a/developing/delta_propagation/implementing_delta_propagation.html.md.erb
+++ /dev/null
@@ -1,24 +0,0 @@

-title:  Implementing Delta Propagation

-
-By default, delta propagation is enabled in your distributed system. When 
enabled, delta propagation is used for objects that implement 
`org.apache.geode.Delta`. You program the methods to store and extract delta 
information for your entries and to apply received delta information.
-
-
-Use the following procedure to implement delta propagation in your distributed 
system.
-
-1.  Study your object types and expected application behavior to determine 
which regions can benefit from using delta propagation. Delta propagation does 
not improve performance for all data and data modification scenarios. See [When 
to Avoid Delta Propagation](when_to_use_delta_prop.html#when_to_use_delta_prop).
-2.  For each region where you are using delta propagation, choose whether to 
enable cloning using the delta propagation property `cloning-enabled`. Cloning 
is disabled by default. See [Delta Propagation 
Properties](delta_propagation_properties.html#delta_propagation_properties).
-3.  If you do not enable cloning, review all associated listener code for 
dependencies on `EntryEvent.getOldValue`. Without cloning, Geode modifies the 
entry in place and so loses its reference to the old value. For delta events, 
the `EntryEvent` methods `getOldValue` and `getNewValue` both return the new 
value.
-4.  For every class where you want delta propagation, implement 
`org.apache.geode.Delta` and update your methods to support delta propagation. 
Exactly how you do this depends on your application and object needs, but these 
steps describe the basic approach:
-1.  If the class is a plain old Java object (POJO), wrap it for this 
implementation and update your code to work with the wrapper class.
-2.  Define as transient any extra object fields that you use to manage 
delta state. This can help performance when the full object is distributed. 
Whenever standard Java serialization is used, the transient keyword indicates 
to Java to not serialize the field.
-3.  Study the object contents to decide how to handle delta changes. Delta 
propagation has the same issues of distributed concurrency control as the 
distribution of full objects, but on a more detailed level. Some parts of your 
objects may be able to change independent of one another while others may 
always need to change together. Send deltas large enough to keep your data 
logically consistent. If, for example, field A and field B depend on each 
other, then your delta distributions should either update both fields or 
neither. As with regular updates, the fewer producers you have on a data 
region, the lower your likelihood of concurrency issues.
-4.  In the application code that puts entries, put the fully populated 
object into the local cache. Even though you are planning to send only deltas, 
errors on the receiving end could cause Geode to request the full object, so 
you must provide it to the originating put method. Do this even in empty 
producers, with regions configured for no local data storage. This usually 
means doing a get on the entry unless you are sure it does not already exist 
anywhere in the distributed region.
-5.  Change each field's update method to record information about the 
update. The information must be sufficient for `toDelta` to encode the delta 
and any additional required delta information when it is invoked.
-6.  Write `hasDelta` to report on whether a delta is available.
-7.  Write `toDelta` to create a byte stream with the changes to the object 
and any other information `fromDelta` will need to apply the changes. Before 
returning from `toDelta`, reset your delta state to indicate that there are no 
delta changes waiting to be sent.
-8.  Write `fromDelta` to decode the byte stream that `toDelta` creates and 
update the object.
-9.  Make sure you provide adequate synchronization to your object to 
maintain a consistent object state. If you do not use cloning, you will 
probably need to synchronize on reads and writes to avoid reading partially 
written updates from the cache.This synchronization might involve `toDelta`, 
`fromDelta`, `toData`, `fromData`, and other methods that access or update the 
object. Additionally, your implementation should take into account the 
possibility of concurrent invocations of `fromDelta` and one or more of the 
object's update methods.
-
-

[21/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/custom_partitioned.svg
--
diff --git a/geode-docs/images_svg/custom_partitioned.svg 
b/geode-docs/images_svg/custom_partitioned.svg
new file mode 100644
index 000..e952a5c
--- /dev/null
+++ b/geode-docs/images_svg/custom_partitioned.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="102 228 392 186" 
width="392pt" height="186pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:07Zcustom_partitioningLayer 
1Member (M1)Partition Region AMember (M2)Partition Region 
Acustomer X 
datacustomer Y datacustomer 
P 
datacustomer Q 
data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/developing_overflow.svg
--
diff --git a/geode-docs/images_svg/developing_overflow.svg 
b/geode-docs/images_svg/developing_overflow.svg
new file mode 100644
index 000..f5cf3bb
--- /dev/null
+++ b/geode-docs/images_svg/developing_overflow.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="77 330 414 138" 
width="414pt" height="138pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:42ZoverflowLayer 1MemberXYZXRegion BDisk 
Filesvalues for 
overflow 
entriesoffload overflowupdate/invalidate/destroysatisfy get<
 /svg>

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/developing_persistence.svg
--
diff --git a/geode-docs/images_svg/developing_persistence.svg 
b/geode-docs/images_svg/developing_persistence.svg
new file mode 100644
index 000..e5f3174
--- /dev/null
+++ b/geode-docs/images_svg/developing_persistence.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="113 479 415 133" 
width="415pt" height="133pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:40ZpersistenceLayer 1MemberXYZXYZRegion Apersist values from createDisk Fileskeys and 
values for all entriesupdate/invalidate/destroy

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/developing_persistence_and_overflow.svg
--
diff --git a/geode-docs/images_svg/developing_persistence_and_overflow.svg 
b/geode-docs/images_svg/developing_persistence_and_overflow.svg
new file mode 100644
index 000..c09ce8e
--- /dev/null
+++ b/geode-docs/images_svg/developing_persistence_and_overflow.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 330 416 139" 
width="416pt" height="139pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:47Zpersist+overflowLayer 
1GemFire MemberXYZXYZRegion 
CDisk Fileskeys and values for all 
entriespersist values from createupdate/invalidate/destroysatisfy get

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_how_1.svg
--
diff --git a/geode-docs/images_svg/distributed_how_1.svg 
b/geode-docs/images_svg/distributed_how_1.svg
new file mode 100644
index 000..4c4026a
--- /dev/null
+++ b/geode-docs/images_svg/distributed_how_1.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 11:12Zhow_it_works-1Layer 
1 Member (M1)Member (M2)X1ApplicationDistributed Region AXDistributed Region 
AX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/distributed_how_2.svg
--
diff --git a/geode-docs/images_svg/distributed_how_2.svg 
b/geode-docs/images_svg/distributed_how_2.svg
new file mode 100644
index 000..ccc6874
--- /dev/null
+++ b/geode-docs/images_svg/distributed_how_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="131 293 355 193" 
width="355pt" height="193pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 

[03/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
--
diff --git 
a/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
 
b/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
new file mode 100644
index 000..50f97b6
--- /dev/null
+++ 
b/geode-docs/managing/troubleshooting/producing_troubleshooting_artifacts.html.md.erb
@@ -0,0 +1,75 @@
+---
+title:  Producing Artifacts for Troubleshooting
+---
+
+There are several types of files that are critical for troubleshooting.
+
+Geode logs and statistics are the two most important artifacts used in 
troubleshooting. In addition, they are required for Geode system health 
verification and performance analysis. For these reasons, logging and 
statistics should always be enabled, especially in production. Save the 
following files for troubleshooting purposes:
+
+-   Log files. Even at the default logging level, the log contains data that 
may be important. Save the whole log, not just the stack. For comparison, save 
log files from before, during, and after the problem occurred.
+-   Statistics archive files.
+-   Core files or stack traces.
+-   For Linux, you can use gdb to extract a stack from a core file.
+-   Crash dumps.
+-   For Windows, save the user mode dump files. Some locations to check for 
these files:
+-   C:\\ProgramData\\Microsoft\\Windows\\WER\\ReportArchive
+-   C:\\ProgramData\\Microsoft\\Windows\\WER\\ReportQueue
+-   
C:\\Users\\*UserProfileName*\\AppData\\Local\\Microsoft\\Windows\\WER\\ReportArchive
+-   
C:\\Users\\*UserProfileName*\\AppData\\Local\\Microsoft\\Windows\\WER\\ReportQueue
+
+When a problem arises that involves more than one process, a network problem 
is the most likely cause. When you diagnose a problem, create a log file for 
each member of all the distributed systems involved. If you are running a 
client/server architecture, create log files for the clients.
+
+**Note:**
+You must run a time synchronization service on all hosts for troubleshooting. 
Synchronized time stamps ensure that log messages on different hosts can be 
merged to accurately reproduce a chronological history of a distributed run.
+
+For each process, complete these steps:
+
+1.  Make sure the host’s clock is synchronized with the other hosts. Use a 
time synchronization tool such as Network Time Protocol (NTP).
+2.  Enable logging to a file instead of standard output by editing 
`gemfire.properties` to include this line:
+
+``` pre
+log-file=filename
+```
+
+3.  Keep the log level at `config` to avoid filling up the disk while 
including configuration information. Add this line to `gemfire.properties`:
+
+``` pre
+log-level=config
+```
+
+**Note:**
+Running with the log level at `fine` can impact system performance and 
fill up your disk.
+
+4.  Enable statistics gathering for the distributed system either by modifying 
`gemfire.properties`:
+
+``` pre
+statistic-sampling-enabled=true
+statistic-archive-file=StatisticsArchiveFile.gfs
+```
+
+or by using the `gfsh alter rutime` command:
+
+``` pre
+alter runtime --group=myMemberGroup --enable-statistics=true 
--statistic-archive-file=StatisticsArchiveFile.gfs
+```
+
+**Note:**
+Collecting statistics at the default sample rate frequency of 1000 
milliseconds does not incur performance overhead.
+
+5.  Run the application again.
+6.  Examine the log files. To get the clearest picture, merge the files. To 
find all the errors in the log file, search for lines that begin with these 
strings:
+
+``` pre
+[error
+[severe
+```
+
+For details on merging log files, see the `--merge-log` argument for the 
[export 
logs](../../tools_modules/gfsh/command-pages/export.html#topic_B80978CC659244AE91E2B8CE56EBDFE3)command.
+
+7.  Export and analyze the stack traces on the member or member group where 
the application is running. Use the `gfsh export stack-traces   
  command`. For example:
+
+``` pre
+gfsh> export stack-traces --file=ApplicationStackTrace.txt --member=member1
+```
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
--
diff --git 
a/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
 
b/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
new file mode 100644
index 000..6c65227
--- /dev/null
+++ 
b/geode-docs/managing/troubleshooting/recovering_conflicting_data_exceptions.html.md.erb
@@ -0,0 +1,58 @@
+---
+title:  Recovering from ConfictingPersistentDataExceptions
+---
+
+A 

[24/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cache_data_loader.svg
--
diff --git a/geode-docs/images_svg/cache_data_loader.svg 
b/geode-docs/images_svg/cache_data_loader.svg
new file mode 100644
index 000..0493df6
--- /dev/null
+++ b/geode-docs/images_svg/cache_data_loader.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="113 230 427 229" 
width="427pt" height="229pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:40Zdata-loadersLayer 1databaseMember (M2)Partitioned Region AYCache LoaderMember (M1)Partitioned Region AXCache 
LoaderMember (M3)Partitioned Region AZCache Loader

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/cache_data_loader_2.svg
--
diff --git a/geode-docs/images_svg/cache_data_loader_2.svg 
b/geode-docs/images_svg/cache_data_loader_2.svg
new file mode 100644
index 000..7334890
--- /dev/null
+++ b/geode-docs/images_svg/cache_data_loader_2.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="95 275 427 229" 
width="427pt" height="229pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 09:41Zdata-loaders-2Layer 
1databaseMember (M2)Distributed Region AXMember (M1)Distributed Region AXCache 
LoaderMember (M3)Distributed Region AX

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/client_server_deployment.svg
--
diff --git a/geode-docs/images_svg/client_server_deployment.svg 
b/geode-docs/images_svg/client_server_deployment.svg
new file mode 100644
index 000..dbaff91
--- /dev/null
+++ b/geode-docs/images_svg/client_server_deployment.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="99 332 374 297" 
width="374pt" height="297pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-07 10:01ZcsLayer 1filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>filter="url(#Shadow)"/>ServerClientLocal Cacheconnection 
poolServer 
FarmLocatorsend address 
and load information to locatorCache Clientsrequest server information from 
locator,locator responds with least loaded serversend, receive cache datareceive server eventsCache Data

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/images_svg/client_server_event_dist.svg
--
diff --git a/geode-docs/images_svg/client_server_event_dist.svg 
b/geode-docs/images_svg/client_server_event_dist.svg
new file mode 100644
index 000..e19e46a
--- /dev/null
+++ b/geode-docs/images_svg/client_server_event_dist.svg
@@ -0,0 +1,3 @@
+
+http://www.w3.org/Graphics/SVG/1.1/DTD/svg11.dtd;>
+http://www.w3.org/2000/svg; 
xmlns:xl="http://www.w3.org/1999/xlink; version="1.1" viewBox="66 203 487 337" 
width="487pt" height="337pt" 
xmlns:dc="http://purl.org/dc/elements/1.1/;> Produced by OmniGraffle 
6.0.5 2015-04-06 22:51Zcs-event-distribution-2Layer 
1Distributed SystemClie
 nt 1Region Apool-name = ServerPoolServerRegion AXClient 2XRegion Apool-name = ServerPoolpool “ServerPool”(with or without subscriptions 
enabled)pool 
“ServerPool”(with 
subscriptions enabled,interest register in X,receiveValues = 
true)Update/CreateXXsubscription12334

[50/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/.gitignore
--
diff --git a/.gitignore b/.gitignore
deleted file mode 100644
index eaf0351..000
--- a/.gitignore
+++ /dev/null
@@ -1,6 +0,0 @@
-geode-book/Gemfile.lock
-geode-book/final_app
-geode-book/output
-out
-temp
-*.bak

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/CONTRIBUTE.md
--
diff --git a/CONTRIBUTE.md b/CONTRIBUTE.md
deleted file mode 100644
index dd97f47..000
--- a/CONTRIBUTE.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# Contributing to the Project Geode Documentation
-
-Project Geode welcomes your contributions to the community's documentation 
efforts. You can participate by writing new content, reviewing and editing 
existing content, or fixing bugs. This document covers the following topics:
-
-- [How to Contribute](#contribute)
-- [Document Source Files and Tools](#source_tools)
-- [Writing Guidelines](#guidelines)
-
-[]()
-
-## How to Contribute
-
-We use the fork-and-pull collaboration method on GitHub:
-
-1. In your GitHub account, fork the gemfire/docs-geode-md repository.
-2. Create a local clone of your fork.
-3. Make changes and commit them in your fork.
-4. In the gemfire/docs-geode-md repository, create a pull request.
-
-See [Using Pull 
Requests](https://help.github.com/articles/using-pull-requests/) on GitHub for 
more about the fork-and-pull collaboration method.
-
-[]()
-
-## Document Source Files and Tools
-
-Project Geode documentation source files are written in markdown. Image files 
include .gif and .png graphics and editable image files in the open source SVG 
format.
-
-- [Working with Markdown Files](#markdown)
-- [Working with Images and Graphics](#images)
-
-[]()
-
-### Working with Markdown Files
-
-You can edit markdown files in any text editor. For more, read [Daring 
Fireball's Markdown Syntax 
page](https://daringfireball.net/projects/markdown/syntax).
-
-[]()
-
-### Working with Images and Graphics
-
-Image files in .gif or .png format are in the `images` directory in the 
Project Geode docs repo. Images in .svg format are in the `images_svg` 
directory.
-
-Most of the Project Geode image files have been converted to the open source 
SVG format. You can insert SVG images directly into an XML topic and modify 
images using a SVG editor.
-
-The Wikipedia page [Comparison of Vector Graphics 
Editors](http://en.wikipedia.org/wiki/Comparison_of_vector_graphics_editors) 
provides a list and comparison of commercial and free vector graphics editors. 
Note, however, that not all of these programs support the SVG format.
-
-[]()
-
-## Writing Guidelines
-
-The most important advice we can provide for working with the Project Geode 
docs is to spend some time becoming familiar with the existing source files and 
the structure of the project directory. In particular, note the following 
conventions and tips:
-
-- Top-level subdirectories organize topics into "books": basic_config, 
configuring, developing, etc.
-
-- Use lowercase characters for all file and directory names. Separate words in 
filenames with an underscore (`_`) character.
-
-- Use the `.md` file extension for topic files.
-
-- Add new topics to the existing directories by subject type. Only create a 
new directory if you are starting a new subject or a new book.
-
-- To start a new topic, you can make a copy of an existing file with similar 
content and edit it.
-
-- Use the appropriate document type for the content you are writing. Create 
multiple topics if you are writing overview, procedural, and reference content.

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/README.md
--
diff --git a/README.md b/README.md
deleted file mode 100644
index a018ca1..000
--- a/README.md
+++ /dev/null
@@ -1,93 +0,0 @@
-# Project Geode End-User Documentation
-
-The latest check-ins to `project-geode/docs` are automatically built and 
published to .
-
-Project Geode provides the full source for end-user documentation in markdown 
format. The markdown can be built into HTML using 
[Bookbinder](https://github.com/pivotal-cf/bookbinder).
-
-Bookbinder is a gem that binds together a unified documentation web 
application from markdown, html, and/or DITA source material. The source 
material for bookbinder must be stored either in local directories or in GitHub 
repositories. Bookbinder runs [middleman](http://middlemanapp.com/) to produce 
a Rackup app that can be deployed locally or as a Web application.
-
-This document contains instructions for building the local Geode documentation 
and publishing it to Cloud Foundry or Pivotal Web Services. It contains the 
sections:
-
-- [Bookbinder Usage](#usage)
-- [Prerequisites](#prereq)
-- [Building the Documentation](#building)
-- 

[37/51] [partial] incubator-geode git commit: GEODE-1952 Consolidated docs under a single geode-docs directory

[dbarnes]

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb
--
diff --git 
a/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb 
b/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb
new file mode 100644
index 000..20cc2c6
--- /dev/null
+++ b/geode-docs/basic_config/the_cache/setting_cache_initializer.html.md.erb
@@ -0,0 +1,59 @@
+---
+title:  Launching an Application after Initializing the Cache
+---
+
+You can specify a callback application that is launched after the cache 
initialization.
+
+By specifying an `` element in your cache.xml file, you can 
trigger a callback application, which is run after the cache has been 
initialized. Applications that use the cacheserver script to start up a server 
can also use this feature to hook into a callback application. To use this 
feature, you need to specify the callback class within the `` 
element. This element should be added to the end of your `cache.xml` file.
+
+You can specify the `` element for either server caches or client 
caches.
+
+The callback class must implement the `Declarable` interface. When the 
callback class is loaded, its `init` method is called, and any parameters 
defined in the `` element are passed as properties.
+
+The following is an example specification.
+
+In cache.xml:
+
+``` pre
+
+   MyInitializer
+  
+ 2
+  
+
+```
+
+Here's the corresponding class definition:
+
+``` pre
+ 
+import org.apache.geode.cache.Declarable;
+
+public class MyInitializer implements Declarable {
+   public void init(Properties properties) {
+  System.out.println(properties.getProperty("members"));
+   }
+}
+```
+
+The following are some additional real-world usage scenarios:
+
+1.  Start a SystemMembershipListener
+
+``` pre
+
+   TestSystemMembershipListener
+
+```
+
+2.  Write a custom tool that monitors cache resources
+
+``` pre
+
+   ResourceMonitorCacheXmlLoader
+
+```
+
+Any singleton or timer task or thread can be instantiated and started using 
the initializer element.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
--
diff --git 
a/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb 
b/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
new file mode 100644
index 000..76d5066
--- /dev/null
+++ b/geode-docs/basic_config/the_cache/setting_cache_properties.html.md.erb
@@ -0,0 +1,22 @@
+---
+title:  Options for Configuring the Cache and Data Regions
+---
+
+To populate your Apache Geode cache and fine-tune its storage and distribution 
behavior, you need to define cached data regions and provide custom 
configuration for the cache and regions.
+
+
+Cache configuration properties define:
+
+-   Cache-wide settings such as disk stores, communication timeouts, and 
settings designating the member as a server
+-   Cache data regions
+
+Configure the cache and its data regions through one or more of these methods:
+
+-   Through a persistent configuration that you define when issuing commands 
that use the gfsh command line utility. `gfsh` supports the administration, 
debugging, and deployment of Apache Geode processes and applications. You can 
use gfsh to configure regions, locators, servers, disk stores, event queues, 
and other objects.
+
+As you issue commands, gfsh saves a set of configurations that apply to 
the entire cluster and also saves configurations that only apply to defined 
groups of members within the cluster. You can re-use these configurations to 
create a distributed system. See [Overview of the Cluster Configuration 
Service](../../configuring/cluster_config/gfsh_persist.html).
+
+-   Through declarations in the XML file named in the `cache-xml-file` 
`gemfire.properties` setting. This file is generally referred to as the 
`cache.xml` file, but it can have any name. See 
[cache.xml](../../reference/topics/chapter_overview_cache_xml.html#cache_xml).
+-   Through application calls to the `org.apache.geode.cache.CacheFactory`, 
`org.apache.geode.cache.Cache` and `org.apache.geode.cache.Region` APIs.
+
+

http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/ccc2fbda/geode-docs/configuring/chapter_overview.html.md.erb
--
diff --git a/geode-docs/configuring/chapter_overview.html.md.erb 
b/geode-docs/configuring/chapter_overview.html.md.erb
new file mode 100644
index 000..8026e72
--- /dev/null
+++ b/geode-docs/configuring/chapter_overview.html.md.erb
@@ -0,0 +1,67 @@
+---
+title:  Configuring and Running a Cluster
+---
+
+You use the `gfsh` command-line utility to configure your Apache Geode cluster