Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 4649B200C2A for ; Tue, 14 Feb 2017 21:11:09 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 426FC160B6A; Tue, 14 Feb 2017 20:11:09 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 33BA3160B5F for ; Tue, 14 Feb 2017 21:11:04 +0100 (CET) Received: (qmail 41527 invoked by uid 500); 14 Feb 2017 20:11:03 -0000 Mailing-List: contact commits-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list commits@geode.apache.org Received: (qmail 40901 invoked by uid 99); 14 Feb 2017 20:11:02 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 14 Feb 2017 20:11:02 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 7B3FCE0A9E; Tue, 14 Feb 2017 20:11:02 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: dbarnes@apache.org To: commits@geode.apache.org Date: Tue, 14 Feb 2017 20:11:13 -0000 Message-Id: <973d5c305fa84bca8b1e737858c739ea@git.apache.org> In-Reply-To: <9f5c8fe4e9e94758ba36921645832f7f@git.apache.org> References: <9f5c8fe4e9e94758ba36921645832f7f@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [12/25] geode-native git commit: Simplify doc directory structure - remove redundant top layer archived-at: Tue, 14 Feb 2017 20:11:09 -0000 http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-book/master_middleman/source/subnavs/gemfire-nc-nav.erb ---------------------------------------------------------------------- diff --git a/geode-docs/docs/geode-native-book/master_middleman/source/subnavs/gemfire-nc-nav.erb b/geode-docs/docs/geode-native-book/master_middleman/source/subnavs/gemfire-nc-nav.erb deleted file mode 100644 index 6d0b752..0000000 --- a/geode-docs/docs/geode-native-book/master_middleman/source/subnavs/gemfire-nc-nav.erb +++ /dev/null @@ -1,985 +0,0 @@ - http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-book/redirects.rb ---------------------------------------------------------------------- diff --git a/geode-docs/docs/geode-native-book/redirects.rb b/geode-docs/docs/geode-native-book/redirects.rb deleted file mode 100644 index bb7d9b7..0000000 --- a/geode-docs/docs/geode-native-book/redirects.rb +++ /dev/null @@ -1,14 +0,0 @@ -r301 %r{/gfmanual/(.*)}, 'http://gemfire.docs.pivotal.io/docs-gemfire/$1' -r301 %r{/geodeman/(.*)}, 'http://gemfire.docs.pivotal.io/docs-gemfire/latest/$1' -r301 %r{/releases/latest/javadoc/(.*)}, 'http://data-docs-samples.cfapps.io/docs-gemfire/821/javadocs/japi/$1' -r301 %r{/docs-gemfire/latest/cpp_api/(.*)}, 'http://data-docs-samples.cfapps.io/docs-gemfire/821/cpp_api/$1' -r301 %r{/docs-gemfire/latest/net_api/(.*)}, 'http://data-docs-samples.cfapps.io/docs-gemfire/821/net_api/$1' -r302 '/index-820.html', 'http://gemfire82.docs.pivotal.io/index.html' -r302 '/index-810.html', 'http://gemfire81.docs.pivotal.io/index.html' -r302 '/index-800.html', 'http://gemfire80.docs.pivotal.io/index.html' -r302 '/index-702.html', 'http://gemfire702.docs.pivotal.io/7.0.2/index.html' -r302 '/index-earlier.html', 'https://www.vmware.com/support/pubs/vfabric-gemfire.html' -r302 '/bugnotes/KnownIssuesGemFire810.html', 'http://gemfire81.docs.pivotal.io/bugnotes/KnownIssuesGemFire810.html' -r302 '/bugnotes/KnownIssuesPulseGemFire810.html', 'http://gemfire81.docs.pivotal.io/bugnotes/KnownIssuesPulseGemFire810.html' -r302 '/bugnotes/KnownIssuesGemFire800.html', 'http://gemfire81.docs.pivotal.io/bugnotes/KnownIssuesGemFire800.html' -r302 '/bugnotes/KnownIssuesPulseGemFire800.html', 'http://gemfire81.docs.pivotal.io/bugnotes/KnownIssuesPulseGemFire800.html' http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/README.md ---------------------------------------------------------------------- diff --git a/geode-docs/docs/geode-native-docs/README.md b/geode-docs/docs/geode-native-docs/README.md deleted file mode 100644 index c19a92a..0000000 --- a/geode-docs/docs/geode-native-docs/README.md +++ /dev/null @@ -1 +0,0 @@ -# docs-gemfire-nc http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/about_native_client_users_guide.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/docs/geode-native-docs/about_native_client_users_guide.html.md.erb b/geode-docs/docs/geode-native-docs/about_native_client_users_guide.html.md.erb deleted file mode 100644 index 707e343..0000000 --- a/geode-docs/docs/geode-native-docs/about_native_client_users_guide.html.md.erb +++ /dev/null @@ -1,85 +0,0 @@ ---- -title: Pivotal GemFire® Native Client 9.0 Documentation ---- - -Published January 5, 2017 - -This documentation provides step-by-step procedures for installation, configuration, and development of native clients. - -- **[Pivotal GemFire Native Client 9.0 Release Notes](relnotes/release_notes_nc-9.0.html)** - -- **[Supported Configurations and System Requirements](getting_started/system_requirements/gemfire_native_client_requirements.html)** - -- **[C++ and .NET API](http://gemfire-apis.docs.pivotal.io)** - -- **[Getting Started with a Native Client](introduction/native-client-intro.html)** - - This section gives you a conceptual overview of the native client. It shows you how to install the product, build native client applications on various platforms, and run the product examples. - -- **[Setting System Properties](setting-properties/chapter-overview.html)** - - *Setting System Properties* describes how to configure Apache Geode native clients and cache servers to participate in a distributed system. - -- **[Configuring the Native Client Cache](client-cache/chapter-overview.html)** - - *Configuring the Native Client Cache* describes the native client cache functionality, initialization file, and APIs. It provides information about creating and working with caches, cache regions, and region entries. - -- **[Pivotal GemFire Native Client C++ API](cpp-caching-api/cpp-caching-api.html)** - - This section describes the primary classes, and usage conventions for the native client C++ API. It demonstrates how to use the API to create caches and perform data serialization. The C++ API documentation is available at [http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io). - -- **[Pivotal GemFire Native Client .NET API](dotnet-caching-api/dotnet-caching-api.html)** - - This section describes the primary classes, usage conventions, and C++ to .NET class mappings of the native client .NET API. It demonstrates how to use the API to create caches and perform data serialization. The .NET API documentation is available at [http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io). - -- **[Preserving Data](preserving-data/preserving-data.html)** - - A server may preserve the data queued and intended to be sent to a native client, such that the data is not discarded if communication between the server and native client is disrupted. Preservation prevents message loss, which can cause a native client to have inconsistent data. Redundant queues and a high availability server implementation may further ensure that queued data is not lost. - -- **[Security](security/overviewsecurity.html)** - - *Security* describes how to implement the security framework for the Geode native client, including authentication, authorization, ecryption, and SSL client/server communication. - -- **[Remote Querying](remote-querying/remote-querying.html)** - - *Remote Querying* documents remote querying from the native client to the Geode cache server. Using examples and procedures, it describes how to use the APIs to run queries against cached data; work with query strings in the native client; create and manage queries; and create indexes. - -- **[Continuous Querying](continuous-querying/continuous-querying.html)** - - *Continuous Querying* describes how to implement continuous querying in the Apache Geode native client so that C++ and .NET clients can run queries against events in the Geode cache server region. It also describes main features and the native client CQ API. - -- **[Using Connection Pools](connection-pools/connection-pools.html)** - - *Using Connection Pools* describes how connection pools achieve load balancing for the client and describes how to configure connection pools as server locators or as a list of servers. - -- **[Transactions](transactions/transactions.html)** - - *Transactions* describes how transactions work on the client side. It provides examples for running, suspending, and resuming transactions. - -- **[Function Execution](function-execution/function-execution.html)** - - *Function Execution* describes how you can execute application functions to achieve linear scalability. It explains how function execution works and lists specific use cases. - -- **[Delta Propagation](delta-propagation/delta-propagation.html)** - - *Delta Propagation* describes how deltas (updates to data) are propagated and how to implement delta propagation. It also analyzes performance limitations. - -- **[Programming Examples](programming-examples/programming-examples.html)** - - This chapter provides a set of programming examples to help you understand the Geode native client API. - -- **[Interoperability of Language Classes and Types](type_mappings/chapter_overview.html)** - - *Interoperability of Language Classes and Types* provides a table that maps C++ class methods to corresponding .NET class methods and a table that maps Java types to .NET types. - -- **[System Statistics](system-statistics/chapter_overview.html)** - - *System Statistics* provides information on the Pivotal GemFire installation and includes standard statistics for caching and distribution activities. - -- **[Installing the SQLite Persistence Manager](sqlite-persistence/chapter_overview.html)** - - *Installing the SQLite Persistence Manager* describes how to download, build and install the SQLite database libraries for use with disk overflow. - -- **[Glossary](glossary.html)** - - This glossary defines terms used in the documentation. http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/cache-init-file/cache-dtd.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/docs/geode-native-docs/cache-init-file/cache-dtd.html.md.erb b/geode-docs/docs/geode-native-docs/cache-init-file/cache-dtd.html.md.erb deleted file mode 100644 index edf11ba..0000000 --- a/geode-docs/docs/geode-native-docs/cache-init-file/cache-dtd.html.md.erb +++ /dev/null @@ -1,267 +0,0 @@ ---- -title: Native Client Cache XML DTD ---- - -The contents of the cache initialization file must conform to the data type definitions in `gfcpp-cache8000.dtd`. - -The `gfcpp-cache8000.dtd` file is in the `productDir/dtd` directory of your native client installation. - -The following example presents the file `gfcpp-cache8000.dtd`, which defines the XML used by the native client for declarative caching. The DTD file identifies the valid element tags that may be present in your XML file, the attributes that correspond to each element, and the valid values for the elements and attributes. - -``` pre - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -``` - - http://git-wip-us.apache.org/repos/asf/geode-native/blob/87b6e035/geode-docs/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb ---------------------------------------------------------------------- diff --git a/geode-docs/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb b/geode-docs/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb deleted file mode 100644 index 8e2ef58..0000000 --- a/geode-docs/docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb +++ /dev/null @@ -1,66 +0,0 @@ ---- -title: Cache Initialization File (cache.xml) ---- - -To ease the task of managing the structure of the cache, you can define the default Geode cache structure in an XML-based initialization file. - -# Cache Initialization File Basics - -The contents of the cache initialization file are used to populate or update a cache. - -This occurs when a cache server starts up, when a client application explicitly creates its cache, or when a client explicitly loads a new structure into an existing cache. - -The initialization file can have any name, but is generally referred to as `cache.xml`. Both client applications and cache servers can use an optional `cache.xml` file to ease the initialization process. - -## File Contents - -The contents of a declarative XML file correspond to APIs declared in the `Cache.hpp` and `Region.hpp` header files. The cache initialization file allows you to accomplish declaratively many of the cache management activities that you can program through the API. - -- The contents of the cache initialization file must conform to the XML definition in _product-dir_/dtd/gfcpp-cache8000.dtd. The DTD file identifies the valid element tags that may be present in your XML file, the attributes that correspond to each element, and the valid values for the elements and attributes. -- The name of the declarative XML file is specified when establishing a connection to the distributed system. You can define it by setting the `cache-xml-file` configuration attribute in the `gfcpp.properties` file for the native client. For details about the `gfcpp.properties` file, see [Setting System and Cache Properties](../setting-properties/chapter-overview.html). - - -# Example cache.xml File - -An example `cache.xml` file shows cache and region initialization for a client, presenting a subset of the possible data configurations. - -Specific information about cache and region attributes is in [Region Attributes](../client-cache/region-attributes.html). Also check the API documentation for `Cache` and `RegionAttributes` at [http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io). - -For information on using a cache with a server pool, see [Using Connection Pools](../connection-pools/connection-pools.html). The example below shows a `cache.xml` file that creates two regions. - -- Region `region1` is defined with a full set of region attributes and application plug-ins. The region's entries have `RegionTimeToLive` and `RegionIdleTimeout` expiration attributes set, as detailed in [Specifying Expiration Attributes](../client-cache/expiration-attributes.html). -- Region `region2` uses mostly default values. - -``` pre - - - - - - - - - - - - - - - - - - - - - - - - - -```