You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by karensmolermiller <gi...@git.apache.org> on 2017/03/28 22:35:28 UTC
[GitHub] geode-native pull request #77: GEODE-2513 Unbrand docs section Configuring t...
GitHub user karensmolermiller opened a pull request:
https://github.com/apache/geode-native/pull/77
GEODE-2513 Unbrand docs section Configuring the Native Client Cache
- namespace updates
- fix typos
@davebarnes97 @joeymcallister @PivotalSarge @echobravopapa @dgkimura @mmartell @mhansonp
Please review, paying particular attention to the namespace changes.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/karensmolermiller/geode-native feature/GEODE-2513-15
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode-native/pull/77.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #77
----
commit 8f4925b775284ff48d0cc9ee20aa328c564aad60
Author: Karen Miller <km...@pivotal.io>
Date: 2017-03-28T22:25:23Z
GEODE-2513 Unbrand docs section Configuring the Native Client Cache
- namespace updates
- fix typos
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] geode-native pull request #77: GEODE-2513 Unbrand docs section Configuring t...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/geode-native/pull/77
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] geode-native pull request #77: GEODE-2513 Unbrand docs section Configuring t...
Posted by PivotalSarge <gi...@git.apache.org>.
Github user PivotalSarge commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/77#discussion_r108701675
--- Diff: docs/geode-native-docs/cache-init-file/chapter-overview.html.md.erb ---
@@ -33,26 +33,23 @@ The initialization file can have any name, but is generally referred to as `cach
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 <code>_product-dir_/dtd/gfcpp-cache8000.dtd</code>. 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 `geode.properties` file for the native client. For details about the `geode.properties` file, see [Setting System and Cache Properties](../setting-properties/chapter-overview.html).
+- The contents of the cache initialization file must conform to the XML definition in [http://geode.apache.org/schema/cache/cache-1.0.xsd](http://geode.apache.org/schema/cache/cache-1.0.xsd). This 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 `geode.properties` file for the client. For details about the `geode.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).
+Specific information about cache and region attributes is in [Region Attributes](../client-cache/region-attributes.html).
-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.
+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 a region.
``` pre
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE cache PUBLIC
- "-//Example Systems, Inc.//Example Declarative Caching 8.0//EN"
- "http://www.example.com/dtd/gfcpp-cache8000.dtd">
+ "-//Example Systems, Inc.//Example Declarative Caching 1.0//EN"
+ "http://geode.apache.org/schema/cache/cache-1.0.xsd">
--- End diff --
Nicely done.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] geode-native pull request #77: GEODE-2513 Unbrand docs section Configuring t...
Posted by PivotalSarge <gi...@git.apache.org>.
Github user PivotalSarge commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/77#discussion_r108702132
--- Diff: docs/geode-native-docs/client-cache/application-plugins.html.md.erb ---
@@ -262,7 +261,7 @@ void removeListener(RegionPtr& region)
## <a id="application-plugins__section_428DCC57B6344603AA19DCAFCE483A10" class="no-quick-link"></a>Considerations for Implementing Callbacks
-Keep your callback implementations lightweight and prevent situations that might cause them to hang. For example, do not perform distribution operations or disconnects inside events.
+Keep your callback implementations lightweight and prevent situations that might cause them to hang. For example, do not perform distribution operations or disconnects inside event handlers.
--- End diff --
More accurate.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---