You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@geode.apache.org by db...@apache.org on 2021/09/08 17:55:06 UTC
[geode-site] branch asf-site updated: Update .NET client guides
with GEODE-7282: Fix capitalization issues
This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/geode-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new d7f57e1 Update .NET client guides with GEODE-7282: Fix capitalization issues
d7f57e1 is described below
commit d7f57e1273b8de44f18abb02202688c95974231c
Author: Dave Barnes <db...@apache.org>
AuthorDate: Wed Sep 8 10:55:01 2021 -0700
Update .NET client guides with GEODE-7282: Fix capitalization issues
---
.../dotnet/112/about-client-users-guide.html | 2 +-
docs/geode-native/dotnet/112/client-cache-ref.html | 2 +-
.../112/configuring/config-client-cache.html | 2 +-
.../dotnet/112/configuring/configuration.html | 2 +-
.../dotnet/112/configuring/sysprops.html | 17 +-
.../configuring/system-level-configuration.html | 2 +-
.../connection-pools/about-connection-pools.html | 2 +-
.../connection-pools/about-server-locators.html | 2 +-
.../connection-pools/client-load-balancing.html | 2 +-
.../112/connection-pools/client-pool-api.html | 2 +-
.../configuring-pools-attributes-example.html | 2 +-
.../112/connection-pools/configuring-pools.html | 2 +-
.../112/connection-pools/connection-pools.html | 2 +-
.../discovering-locators-dynamically.html | 2 +-
.../running-connection-pool-code.html | 2 +-
.../connection-pools/subscription-properties.html | 2 +-
.../dotnet/112/continuous-queries.html | 11 +-
.../dotnet/112/function-execution.html | 40 +--
.../app-dev-walkthrough-dotnet.html | 2 +-
.../getting-started/getting-started-nc-client.html | 2 +-
.../112/getting-started/put-get-example.html | 2 +-
.../preserving-data/app-ops-during-int-reg.html | 2 +-
.../112/preserving-data/client-side-config.html | 2 +-
.../config-durable-interest-keys.html | 16 +-
.../preserving-data/config-durable-reconnect.html | 2 +-
.../preserving-data/configuring-durable-nc.html | 2 +-
.../112/preserving-data/configuring-nc-ha.html | 2 +-
.../preserving-data/disconnecting-from-server.html | 2 +-
.../dotnet/112/preserving-data/disconnection.html | 2 +-
.../preserving-data/durable-client-life-cycle.html | 2 +-
.../durable-client-messaging-req.html | 2 +-
.../preserving-data/durable-client-messaging.html | 2 +-
.../preserving-data/durable-message-replay.html | 2 +-
.../high-availability-client-server.html | 2 +-
.../impl-cache-listeners-durable-clients.html | 2 +-
.../112/preserving-data/initial-operation.html | 2 +-
.../112/preserving-data/preserving-data.html | 2 +-
.../dotnet/112/preserving-data/reconnection.html | 2 +-
.../sending-cache-ready-message.html | 2 +-
.../112/preserving-data/sending-periodic-ack.html | 2 +-
.../preserving-data/using-queue-conflation.html | 2 +-
.../regions/consistency-checking-in-regions.html | 2 +-
.../dotnet/112/regions/region-attributes.html | 2 +-
docs/geode-native/dotnet/112/regions/regions.html | 2 +-
.../regions/registering-interest-for-entries.html | 38 +--
docs/geode-native/dotnet/112/remote-queries.html | 7 +-
.../dotnet/112/security/authentication.html | 2 +-
.../dotnet/112/security/security-systemprops.html | 324 ---------------------
.../geode-native/dotnet/112/security/security.html | 2 +-
.../dotnet/112/security/sslclientserver.html | 4 +-
.../112/serialization/data-serialization.html | 2 +-
.../custom-class-igfserializable.html | 2 +-
.../dotnet-data-serialization-options.html | 2 +-
.../dotnet-data-serialization.html | 2 +-
.../dotnet-pdx-autoserializer.html | 2 +-
.../dotnet-pdx-serialization-features.html | 2 +-
.../dotnet-pdx-serialization.html | 2 +-
.../extending-pdx-autoserializer.html | 2 +-
.../how-igfserializable-works.html | 2 +-
.../implementing-igfserializable.html | 2 +-
.../mapping-dotnet-domain-type-names.html | 2 +-
.../programming-ipdxinstance.html | 2 +-
.../dotnet-serialization/registering-the-type.html | 2 +-
.../dotnet-serialization/serializable-types.html | 2 +-
.../serialize-using-igfserializable.html | 2 +-
.../serialize-using-ipdxserializable.html | 6 +-
.../serializing-domain-objects.html | 2 +-
.../using-ipdxinstancefactory.html | 2 +-
docs/geode-native/dotnet/112/transactions.html | 10 +-
.../dotnet/113/continuous-queries.html | 9 +-
.../dotnet/113/function-execution.html | 38 +--
.../config-durable-interest-keys.html | 14 +-
.../regions/registering-interest-for-entries.html | 36 +--
docs/geode-native/dotnet/113/remote-queries.html | 5 +-
.../dotnet-pdx-autoserializer.html | 4 +-
.../pdx-serializable-examples.html | 4 +-
.../serialize-using-ipdxserializable.html | 4 +-
docs/geode-native/dotnet/113/transactions.html | 8 +-
.../dotnet/114/continuous-queries.html | 6 +-
.../dotnet/114/function-execution.html | 38 +--
.../config-durable-interest-keys.html | 14 +-
.../regions/registering-interest-for-entries.html | 36 +--
docs/geode-native/dotnet/114/remote-queries.html | 2 +-
.../dotnet-pdx-autoserializer.html | 4 +-
.../pdx-serializable-examples.html | 2 +-
.../serialize-using-ipdxserializable.html | 4 +-
docs/geode-native/dotnet/114/transactions.html | 8 +-
87 files changed, 250 insertions(+), 577 deletions(-)
diff --git a/docs/geode-native/dotnet/112/about-client-users-guide.html b/docs/geode-native/dotnet/112/about-client-users-guide.html
index 46a2b48..6ca221f 100644
--- a/docs/geode-native/dotnet/112/about-client-users-guide.html
+++ b/docs/geode-native/dotnet/112/about-client-users-guide.html
@@ -288,7 +288,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/client-cache-ref.html b/docs/geode-native/dotnet/112/client-cache-ref.html
index 7e2b594..065d886 100644
--- a/docs/geode-native/dotnet/112/client-cache-ref.html
+++ b/docs/geode-native/dotnet/112/client-cache-ref.html
@@ -1023,7 +1023,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/configuring/config-client-cache.html b/docs/geode-native/dotnet/112/configuring/config-client-cache.html
index f2f4a70..c765dc4 100644
--- a/docs/geode-native/dotnet/112/configuring/config-client-cache.html
+++ b/docs/geode-native/dotnet/112/configuring/config-client-cache.html
@@ -288,7 +288,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/configuring/configuration.html b/docs/geode-native/dotnet/112/configuring/configuration.html
index bf67ddf..e804d98 100644
--- a/docs/geode-native/dotnet/112/configuring/configuration.html
+++ b/docs/geode-native/dotnet/112/configuring/configuration.html
@@ -308,7 +308,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/configuring/sysprops.html b/docs/geode-native/dotnet/112/configuring/sysprops.html
index 6175fc9..f70c7c6 100644
--- a/docs/geode-native/dotnet/112/configuring/sysprops.html
+++ b/docs/geode-native/dotnet/112/configuring/sysprops.html
@@ -485,21 +485,6 @@ When the chunk handler is not operative (enable-chunk-handler=false), each appli
</tr>
</thead>
<tbody>
-<tr class="odd">
-<td><code class="ph codeph">security-client-auth-factory</code></td>
-<td>Sets the key for the <code class="ph codeph">AuthInitialize</code> factory function.</td>
-<td>empty</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">security-client-auth-library</code></td>
-<td>Registers the path to the <code class="ph codeph">securityImpl.dll</code> library.</td>
-<td>empty</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">security-client-dhalgo</code></td>
-<td>Diffie-Hellman based credentials encryption is not supported.</td>
-<td>null</td>
-</tr>
<tr class="even">
<td><code class="ph codeph">security-client-kspath</code></td>
<td>Path to a .PEM file, which contains the public certificates for all Geode cache servers to which the client can connect through specified endpoints.</td>
@@ -581,7 +566,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/configuring/system-level-configuration.html b/docs/geode-native/dotnet/112/configuring/system-level-configuration.html
index 9f1c37e..67c9b7e 100644
--- a/docs/geode-native/dotnet/112/configuring/system-level-configuration.html
+++ b/docs/geode-native/dotnet/112/configuring/system-level-configuration.html
@@ -392,7 +392,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/about-connection-pools.html b/docs/geode-native/dotnet/112/connection-pools/about-connection-pools.html
index 35cb668..0a91f87 100644
--- a/docs/geode-native/dotnet/112/connection-pools/about-connection-pools.html
+++ b/docs/geode-native/dotnet/112/connection-pools/about-connection-pools.html
@@ -288,7 +288,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/about-server-locators.html b/docs/geode-native/dotnet/112/connection-pools/about-server-locators.html
index 4343a3a..065cf3e 100644
--- a/docs/geode-native/dotnet/112/connection-pools/about-server-locators.html
+++ b/docs/geode-native/dotnet/112/connection-pools/about-server-locators.html
@@ -287,7 +287,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/client-load-balancing.html b/docs/geode-native/dotnet/112/connection-pools/client-load-balancing.html
index 2fbc605..2b5d62a 100644
--- a/docs/geode-native/dotnet/112/connection-pools/client-load-balancing.html
+++ b/docs/geode-native/dotnet/112/connection-pools/client-load-balancing.html
@@ -289,7 +289,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/client-pool-api.html b/docs/geode-native/dotnet/112/connection-pools/client-pool-api.html
index b58b087..8796c79 100644
--- a/docs/geode-native/dotnet/112/connection-pools/client-pool-api.html
+++ b/docs/geode-native/dotnet/112/connection-pools/client-pool-api.html
@@ -292,7 +292,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/configuring-pools-attributes-example.html b/docs/geode-native/dotnet/112/connection-pools/configuring-pools-attributes-example.html
index 55784e8..12716f9 100644
--- a/docs/geode-native/dotnet/112/connection-pools/configuring-pools-attributes-example.html
+++ b/docs/geode-native/dotnet/112/connection-pools/configuring-pools-attributes-example.html
@@ -424,7 +424,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/configuring-pools.html b/docs/geode-native/dotnet/112/connection-pools/configuring-pools.html
index fb8a563..ef0bf6b 100644
--- a/docs/geode-native/dotnet/112/connection-pools/configuring-pools.html
+++ b/docs/geode-native/dotnet/112/connection-pools/configuring-pools.html
@@ -292,7 +292,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/connection-pools.html b/docs/geode-native/dotnet/112/connection-pools/connection-pools.html
index 8476343..6d3609b 100644
--- a/docs/geode-native/dotnet/112/connection-pools/connection-pools.html
+++ b/docs/geode-native/dotnet/112/connection-pools/connection-pools.html
@@ -284,7 +284,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/discovering-locators-dynamically.html b/docs/geode-native/dotnet/112/connection-pools/discovering-locators-dynamically.html
index b6a4218..5bcb9ca 100644
--- a/docs/geode-native/dotnet/112/connection-pools/discovering-locators-dynamically.html
+++ b/docs/geode-native/dotnet/112/connection-pools/discovering-locators-dynamically.html
@@ -285,7 +285,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/running-connection-pool-code.html b/docs/geode-native/dotnet/112/connection-pools/running-connection-pool-code.html
index f27a22d..dc478c0 100644
--- a/docs/geode-native/dotnet/112/connection-pools/running-connection-pool-code.html
+++ b/docs/geode-native/dotnet/112/connection-pools/running-connection-pool-code.html
@@ -323,7 +323,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/connection-pools/subscription-properties.html b/docs/geode-native/dotnet/112/connection-pools/subscription-properties.html
index 9c37075..a47db5a 100644
--- a/docs/geode-native/dotnet/112/connection-pools/subscription-properties.html
+++ b/docs/geode-native/dotnet/112/connection-pools/subscription-properties.html
@@ -294,7 +294,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/continuous-queries.html b/docs/geode-native/dotnet/112/continuous-queries.html
index e4ae5e6..a7b1737 100644
--- a/docs/geode-native/dotnet/112/continuous-queries.html
+++ b/docs/geode-native/dotnet/112/continuous-queries.html
@@ -274,18 +274,21 @@ Compare this to register interest by reviewing <a href="/docs/geode-native/dotne
<li><p><strong>Active query execution</strong>. Once initialized, the queries operate on new events. Events that change the query result are sent to the client immediately.</p></li>
</ul>
+<p><strong>Note:</strong> Because floating point numbers can not reliably be compared for equality, do not use
+floating point values as keys or key components when constructing a query.</p>
+
<h2 id="typical-continuous-query-lifecycle"><a id="cq_api"></a>Typical Continuous Query Lifecycle</h2>
<ol>
<li> The client creates the CQ. This sets up everything for running the query and provides the client with a <code>CqQuery</code> object, but does not execute the CQ. At this point, the query is in a <code>STOPPED</code>state, ready to be closed or run.</li>
-<li><p>The client initiates the CQ with an API call to one of the <code>CqQuery execute*</code> methods. This puts the query into a <code>RUNNING</code> state on the client and on the server. The server remotely evaluates the query string, and optionally returns the results to the client. <code>CqQuery execute*</code> methods include:</p>
+<li><p>The client initiates the CQ with an API call to one of the <code>CqQuery Execute*</code> methods. This puts the query into a <code>RUNNING</code> state on the client and on the server. The server remotely evaluates the query string, and optionally returns the results to the client. <code>CqQuery Execute*</code> methods include:</p>
<ul>
<li><code>CqQuery.Execute()</code></li>
<li><code>CqQuery.ExecuteWithInitialResults()</code></li>
</ul></li>
<li><p>A CQ Listener waits for events. When it receives events, it takes action accordingly with the data in the CqEvent.</p></li>
-<li><p>The CQ is closed by a client call to <code>CqQuery.close</code>. This de-allocates all resources in use for the CQ on the client and server. At this point, the cycle could begin again with the creation of a new <code>CqQuery</code> instance.</p></li>
+<li><p>The CQ is closed by a client call to <code>CqQuery.Close</code>. This de-allocates all resources in use for the CQ on the client and server. At this point, the cycle could begin again with the creation of a new <code>CqQuery</code> instance.</p></li>
</ol>
<h2 id="executing-a-continuous-query-from-the-client"><a id="ExecutingACQ"></a>Executing a Continuous Query from the Client</h2>
@@ -295,7 +298,7 @@ Compare this to register interest by reviewing <a href="/docs/geode-native/dotne
<ol>
<li> Create an instance of the <code>QueryService</code> class. If you are using the pool API (recommended), you should obtain the <code>QueryService</code> from the pool.</li>
<li> Define a CQ Listener (an <code>ICqListener</code>) to field events sent from the server.</li>
-<li> Use one of the <code>CqQuery execute*</code> methods to submit the query string to the cache server.</li>
+<li> Use one of the <code>CqQuery Execute*</code> methods to submit the query string to the cache server.</li>
<li> The server remotely evaluates the query string, then monitors those results and notifies the client if they change.</li>
<li> The client listens for changes that match the query predicate.</li>
<li> Iterate through the returned objects.</li>
@@ -393,7 +396,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/function-execution.html b/docs/geode-native/dotnet/112/function-execution.html
index ecf8c71..6ceb7d5 100644
--- a/docs/geode-native/dotnet/112/function-execution.html
+++ b/docs/geode-native/dotnet/112/function-execution.html
@@ -273,36 +273,36 @@ in the Geode User Guide for details on how to write and register server-resident
<h2 id="how-functions-execute"><a id="nc-fe-how_functions_execute"></a>How Functions Execute</h2>
<ol>
-<li> The calling client application runs the <code>execute</code> method on the <code>Execution</code> object. The function must already be registered on the servers.</li>
-<li> The function is invoked on the servers where it needs to run. The servers are determined by the <code>FunctionService on*</code>
+<li> The calling client application runs the <code>Execute</code> method on the <code>Execution</code> object. The function must already be registered on the servers.</li>
+<li> The function is invoked on the servers where it needs to run. The servers are determined by the <code>FunctionService On*</code>
method calls, region configuration, and any filters.</li>
<li> If the function has results, the result is returned in a <code>ResultCollector</code> object.</li>
-<li> The client collects results using the <code>ResultCollector.getResult()</code> method.</li>
+<li> The client collects results using the <code>ResultCollector.GetResult()</code> method.</li>
</ol>
<p>In every client where you want to execute the function and process the results:</p>
<ul>
-<li>Use one of the <code>FunctionService on*</code> methods to create an <code>Execution</code> object. The <code>on*</code> methods,
-<code>onRegion</code>, <code>onServer</code> and <code>onServers</code>, define the highest level where the function is run.</li>
-<li>If you use <code>onRegion</code> you can further narrow your run scope by setting key filters.</li>
-<li>A function run using <code>onRegion</code> is a <em>data dependent</em> function – others are <em>data-independent</em> functions.</li>
+<li>Use one of the <code>FunctionService On*</code> methods to create an <code>Execution</code> object. The <code>On*</code> methods,
+<code>OnRegion</code>, <code>OnServer</code> and <code>OnServers</code>, define the highest level where the function is run.</li>
+<li>If you use <code>OnRegion</code> you can further narrow your run scope by setting key filters.</li>
+<li>A function run using <code>OnRegion</code> is a <em>data dependent</em> function – others are <em>data-independent</em> functions.</li>
<li><p>You can run a data dependent function against partitioned and colocated partitioned regions. From the client, provide the appropriate key
sets to the function call.</p></li>
<li><p>The <code>Execution</code> object allows you to customize the invocation by:</p>
<ul>
-<li> Providing a set of data keys to <code>withFilter</code> to narrow the execution scope. This works only for <code>onRegion</code> Execution objects (data-dependent functions).</li>
-<li> Providing function arguments to <code>withArgs</code>.</li>
-<li> Defining a custom <code>ResultCollector</code> for <code>withCollector</code>.</li>
+<li> Providing a set of data keys to <code>WithFilter</code> to narrow the execution scope. This works only for <code>OnRegion</code> Execution objects (data-dependent functions).</li>
+<li> Providing function arguments to <code>WithArgs</code>.</li>
+<li> Defining a custom <code>ResultCollector</code> for <code>WithCollector</code>.</li>
</ul></li>
-<li><p>Call the <code>Execution.execute()</code> method to run the function.</p></li>
+<li><p>Call the <code>Execution.Execute()</code> method to run the function.</p></li>
</ul>
<h2 id="processing-function-results"><a id="nc-fe-processing_function_results"></a>Processing Function Results</h2>
<p>To get the results from the function in the client app, use the result collector returned from the function execution.
-The <code>getResult</code> methods of the default result collector block until all results are received, then return the full result set.</p>
+The <code>GetResult</code> methods of the default result collector block until all results are received, then return the full result set.</p>
<p>The client can use the default result collector. If the client needs special results handling, code a custom <code>ResultsCollector</code> implementation to replace the default.
Use the <code>Execution::withCollector</code> method to specify the custom collector.
@@ -312,12 +312,12 @@ To handle the results in a custom manner:</p>
<li> Write a class that implements the <code>ResultCollector</code> interface to handle the results in a custom manner. The methods are of two types: one handles data and information from Geode and populates the results set, while the other returns the compiled results to the calling application:
<ul>
-<li> <code>addResult</code> is called when results arrive from the <code>Function</code> methods. Use <code>addResult</code> to add a single result to the ResultCollector.</li>
-<li> <code>endResults</code> is called to signal the end of all results from the function execution.</li>
-<li> <code>getResult</code> is available to your executing application (the one that calls <code>Execution.execute</code>) to retrieve the results. This may block until all results are available.</li>
-<li> <code>clearResults</code> is called to clear partial results from the results collector. This is used only for highly available <code>onRegion</code> functions where the calling application waits for the results. If the call fails, before Geode retries the execution, it calls <code>clearResults</code> to ready the instance for a clean set of results.</li>
+<li> <code>AddResult</code> is called when results arrive from the <code>Function</code> methods. Use <code>AddResult</code> to add a single result to the ResultCollector.</li>
+<li> <code>EndResults</code> is called to signal the end of all results from the function execution.</li>
+<li> <code>GetResult</code> is available to your executing application (the one that calls <code>Execution.Execute</code>) to retrieve the results. This may block until all results are available.</li>
+<li> <code>ClearResults</code> is called to clear partial results from the results collector. This is used only for highly available <code>OnRegion</code> functions where the calling application waits for the results. If the call fails, before Geode retries the execution, it calls <code>ClearResults</code> to ready the instance for a clean set of results.</li>
</ul></li>
-<li> Use the <code>Execution</code> object in your executing member to call <code>withCollector</code>, passing your custom collector.</li>
+<li> Use the <code>Execution</code> object in your executing member to call <code>WithCollector</code>, passing your custom collector.</li>
</ol>
<h2 id="function-execution-example"><a id="nc-fe-examples"></a>Function Execution Example</h2>
@@ -329,7 +329,7 @@ To handle the results in a custom manner:</p>
<li>The function is preloaded with a JAR file containing the server-side Java function code. </li>
<li>The function, called “ExampleMultiGetFunction”, is defined in the
<code>examples/utilities</code> directory of your distribution. As its input parameter, the function takes an array of keys,
-then performs a <code>get</code> on each key and returns an array containing the results.</li>
+then performs a <code>Get</code> on each key and returns an array containing the results.</li>
<li>The function does not load values into the data store. That is a separate operation, performed in these examples by
the client, and does not involve the server-side function.</li>
</ul>
@@ -346,7 +346,7 @@ of the input parameter and return value.</p>
</ul>
<p>If the client expects results, it must create a result object.
-The .NET example uses a built-in result collector (<code>IResultCollector.getResults()</code>) to retrieve the function results.</p>
+The .NET example uses a built-in result collector (<code>IResultCollector.GetResults()</code>) to retrieve the function results.</p>
<h3 id=".net-example"><a id="nc-fe-dotnet_example"></a>.NET Example</h3>
@@ -446,7 +446,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/getting-started/app-dev-walkthrough-dotnet.html b/docs/geode-native/dotnet/112/getting-started/app-dev-walkthrough-dotnet.html
index 943cc42..6c15272 100644
--- a/docs/geode-native/dotnet/112/getting-started/app-dev-walkthrough-dotnet.html
+++ b/docs/geode-native/dotnet/112/getting-started/app-dev-walkthrough-dotnet.html
@@ -375,7 +375,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html b/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html
index 78490da..3be0e5a 100644
--- a/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html
+++ b/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html
@@ -386,7 +386,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/getting-started/put-get-example.html b/docs/geode-native/dotnet/112/getting-started/put-get-example.html
index 7da25b9..db00c70 100644
--- a/docs/geode-native/dotnet/112/getting-started/put-get-example.html
+++ b/docs/geode-native/dotnet/112/getting-started/put-get-example.html
@@ -333,7 +333,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/app-ops-during-int-reg.html b/docs/geode-native/dotnet/112/preserving-data/app-ops-during-int-reg.html
index 6f7681a..4704e2a 100644
--- a/docs/geode-native/dotnet/112/preserving-data/app-ops-during-int-reg.html
+++ b/docs/geode-native/dotnet/112/preserving-data/app-ops-during-int-reg.html
@@ -287,7 +287,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/client-side-config.html b/docs/geode-native/dotnet/112/preserving-data/client-side-config.html
index fea3092..a9a4f0e 100644
--- a/docs/geode-native/dotnet/112/preserving-data/client-side-config.html
+++ b/docs/geode-native/dotnet/112/preserving-data/client-side-config.html
@@ -287,7 +287,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/config-durable-interest-keys.html b/docs/geode-native/dotnet/112/preserving-data/config-durable-interest-keys.html
index 8d5d062..d013a01 100644
--- a/docs/geode-native/dotnet/112/preserving-data/config-durable-interest-keys.html
+++ b/docs/geode-native/dotnet/112/preserving-data/config-durable-interest-keys.html
@@ -9,7 +9,6 @@
<link href='https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,300italic,400italic,400,600' rel='stylesheet' type='text/css'>
<!-- Use title if it's in the page YAML frontmatter -->
<title>
- Configuring Durable Interest in Keys |
Geode Native .NET Docs
</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -217,9 +216,6 @@ 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.
-->
- <h1 class="title-container" >
- Configuring Durable Interest in Keys
- </h1>
<div id="js-quick-links" >
@@ -227,7 +223,11 @@ limitations under the License.
<div class="to-top" id="js-to-top">
<a href="#top" title="back to top"></a>
</div>
- <!--
+ <p>–</p>
+
+<h2 id="title:-configuring-durable-interest-in-keys">title: Configuring Durable Interest in Keys</h2>
+
+<!--
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.
@@ -250,7 +250,7 @@ limitations under the License.
<p>You still register interest for other keys, but not durable interest. When the client is connected to its servers, it receives messages for those non-durable keys. When the client is disconnected, its non-durable interest registrations are deleted but messages that are already in the queue remain there.</p>
-<p>For durable clients, all interest registration is done immediately after the regions are created. This is required whether interest registration is durable or not durable. An extra <code>registerInterest</code> parameter specified for durable clients indicates whether the registration is durable (true) or not (false).</p>
+<p>For durable clients, all interest registration is done immediately after the regions are created. This is required whether interest registration is durable or not durable. An extra <code>RegisterInterest</code> parameter specified for durable clients indicates whether the registration is durable (true) or not (false).</p>
<h2 id="api-client-durable-interest-list-registration-(c++)">API Client Durable Interest List Registration (C++)</h2>
@@ -259,7 +259,7 @@ limitations under the License.
// durable (true) or nondurable(default).
VectorOfCacheableKey keys;
keys.push_back( CacheableString::create("Key-1") );
-regionPtr->registerKeys(keys,true);
+regionPtr->RegisterKeys(keys,true);
</code></pre>
<p><a id="concept_6456354A9AD945C780A5AA864B41B564__section_3DE5872B0888410EB42D52CFB28C79E5"></a>
@@ -299,7 +299,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/config-durable-reconnect.html b/docs/geode-native/dotnet/112/preserving-data/config-durable-reconnect.html
index c88ed89..b12873a 100644
--- a/docs/geode-native/dotnet/112/preserving-data/config-durable-reconnect.html
+++ b/docs/geode-native/dotnet/112/preserving-data/config-durable-reconnect.html
@@ -311,7 +311,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/configuring-durable-nc.html b/docs/geode-native/dotnet/112/preserving-data/configuring-durable-nc.html
index 1bbccb2..283482b 100644
--- a/docs/geode-native/dotnet/112/preserving-data/configuring-durable-nc.html
+++ b/docs/geode-native/dotnet/112/preserving-data/configuring-durable-nc.html
@@ -303,7 +303,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/configuring-nc-ha.html b/docs/geode-native/dotnet/112/preserving-data/configuring-nc-ha.html
index 9026f00..19632ff 100644
--- a/docs/geode-native/dotnet/112/preserving-data/configuring-nc-ha.html
+++ b/docs/geode-native/dotnet/112/preserving-data/configuring-nc-ha.html
@@ -312,7 +312,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/disconnecting-from-server.html b/docs/geode-native/dotnet/112/preserving-data/disconnecting-from-server.html
index 1ef94c5..d7abc59 100644
--- a/docs/geode-native/dotnet/112/preserving-data/disconnecting-from-server.html
+++ b/docs/geode-native/dotnet/112/preserving-data/disconnecting-from-server.html
@@ -285,7 +285,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/disconnection.html b/docs/geode-native/dotnet/112/preserving-data/disconnection.html
index e28f4ee..403de70 100644
--- a/docs/geode-native/dotnet/112/preserving-data/disconnection.html
+++ b/docs/geode-native/dotnet/112/preserving-data/disconnection.html
@@ -295,7 +295,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/durable-client-life-cycle.html b/docs/geode-native/dotnet/112/preserving-data/durable-client-life-cycle.html
index b6ce8dd..193e9f5 100644
--- a/docs/geode-native/dotnet/112/preserving-data/durable-client-life-cycle.html
+++ b/docs/geode-native/dotnet/112/preserving-data/durable-client-life-cycle.html
@@ -293,7 +293,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging-req.html b/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging-req.html
index 1162c3e..7c3c7b2 100644
--- a/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging-req.html
+++ b/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging-req.html
@@ -290,7 +290,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging.html b/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging.html
index 966263f..a1266a2 100644
--- a/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging.html
+++ b/docs/geode-native/dotnet/112/preserving-data/durable-client-messaging.html
@@ -296,7 +296,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/durable-message-replay.html b/docs/geode-native/dotnet/112/preserving-data/durable-message-replay.html
index 91b50e3..931d68a 100644
--- a/docs/geode-native/dotnet/112/preserving-data/durable-message-replay.html
+++ b/docs/geode-native/dotnet/112/preserving-data/durable-message-replay.html
@@ -295,7 +295,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/high-availability-client-server.html b/docs/geode-native/dotnet/112/preserving-data/high-availability-client-server.html
index 8dbc2ed..8e132bd 100644
--- a/docs/geode-native/dotnet/112/preserving-data/high-availability-client-server.html
+++ b/docs/geode-native/dotnet/112/preserving-data/high-availability-client-server.html
@@ -286,7 +286,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/impl-cache-listeners-durable-clients.html b/docs/geode-native/dotnet/112/preserving-data/impl-cache-listeners-durable-clients.html
index 18de09f..84c7098 100644
--- a/docs/geode-native/dotnet/112/preserving-data/impl-cache-listeners-durable-clients.html
+++ b/docs/geode-native/dotnet/112/preserving-data/impl-cache-listeners-durable-clients.html
@@ -289,7 +289,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/initial-operation.html b/docs/geode-native/dotnet/112/preserving-data/initial-operation.html
index 8f59419..5a6ec44 100644
--- a/docs/geode-native/dotnet/112/preserving-data/initial-operation.html
+++ b/docs/geode-native/dotnet/112/preserving-data/initial-operation.html
@@ -277,7 +277,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/preserving-data.html b/docs/geode-native/dotnet/112/preserving-data/preserving-data.html
index 45382fc..d190c8b 100644
--- a/docs/geode-native/dotnet/112/preserving-data/preserving-data.html
+++ b/docs/geode-native/dotnet/112/preserving-data/preserving-data.html
@@ -289,7 +289,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/reconnection.html b/docs/geode-native/dotnet/112/preserving-data/reconnection.html
index 77538df..a07c8af 100644
--- a/docs/geode-native/dotnet/112/preserving-data/reconnection.html
+++ b/docs/geode-native/dotnet/112/preserving-data/reconnection.html
@@ -306,7 +306,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/sending-cache-ready-message.html b/docs/geode-native/dotnet/112/preserving-data/sending-cache-ready-message.html
index cb999bd..195cd4e 100644
--- a/docs/geode-native/dotnet/112/preserving-data/sending-cache-ready-message.html
+++ b/docs/geode-native/dotnet/112/preserving-data/sending-cache-ready-message.html
@@ -285,7 +285,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/sending-periodic-ack.html b/docs/geode-native/dotnet/112/preserving-data/sending-periodic-ack.html
index 8475ea2..d880520 100644
--- a/docs/geode-native/dotnet/112/preserving-data/sending-periodic-ack.html
+++ b/docs/geode-native/dotnet/112/preserving-data/sending-periodic-ack.html
@@ -299,7 +299,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/preserving-data/using-queue-conflation.html b/docs/geode-native/dotnet/112/preserving-data/using-queue-conflation.html
index 7b768f0..9adeeb7 100644
--- a/docs/geode-native/dotnet/112/preserving-data/using-queue-conflation.html
+++ b/docs/geode-native/dotnet/112/preserving-data/using-queue-conflation.html
@@ -295,7 +295,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/regions/consistency-checking-in-regions.html b/docs/geode-native/dotnet/112/regions/consistency-checking-in-regions.html
index 8fd826f..cff87a5 100644
--- a/docs/geode-native/dotnet/112/regions/consistency-checking-in-regions.html
+++ b/docs/geode-native/dotnet/112/regions/consistency-checking-in-regions.html
@@ -287,7 +287,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/regions/region-attributes.html b/docs/geode-native/dotnet/112/regions/region-attributes.html
index 83a2cef..13b9270 100644
--- a/docs/geode-native/dotnet/112/regions/region-attributes.html
+++ b/docs/geode-native/dotnet/112/regions/region-attributes.html
@@ -321,7 +321,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/regions/regions.html b/docs/geode-native/dotnet/112/regions/regions.html
index 6a1a2c8..fd3779c 100644
--- a/docs/geode-native/dotnet/112/regions/regions.html
+++ b/docs/geode-native/dotnet/112/regions/regions.html
@@ -434,7 +434,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/regions/registering-interest-for-entries.html b/docs/geode-native/dotnet/112/regions/registering-interest-for-entries.html
index 34c29ac..528ea29 100644
--- a/docs/geode-native/dotnet/112/regions/registering-interest-for-entries.html
+++ b/docs/geode-native/dotnet/112/regions/registering-interest-for-entries.html
@@ -248,17 +248,17 @@ limitations under the License.
<p>You can register interest for specific entry keys or for all keys. Regular expressions can be used to register interest for keys whose strings match the expression. You can also unregister interest for specific keys, groups of keys based on regular expressions, or for all keys.</p>
-<p><strong>Note:</strong> Interest registration and unregistration are symmetrical operations. Consequently, you cannot register interest in all keys and then unregister interest in a specific set of keys. Also, if you first register interest in specific keys with <code>registerKeys</code>, then call <code>registerAllKeys</code>, you must call <code>unregisterAllKeys</code> before specifying interest in specific keys again.</p>
+<p><strong>Note:</strong> Interest registration and unregistration are symmetrical operations. Consequently, you cannot register interest in all keys and then unregister interest in a specific set of keys. Also, if you first register interest in specific keys with <code>RegisterKeys</code>, then call <code>RegisterAllKeys</code>, you must call <code>UnregisterAllKeys</code> before specifying interest in specific keys again.</p>
<h2 id="client-api-for-registering-interest"><a id="registering-interest-for-entries__section_C9A3D7F193B24ACD83B2D67813E596A0" class="no-quick-link"></a>Client API for Registering Interest</h2>
<p>You register client interest through the .NET API. The .NET API provides the <code>RegisterKeys</code>, <code>RegisterAllKeys</code>, and <code>RegisterRegex</code> methods, with corresponding unregistration accomplished using the <code>UnregisterKeys</code>, <code>UnregisterAllKeys</code>, and <code>UnregisterRegex</code> methods.</p>
-<p>The <code>registerKeys</code>, <code>registerRegex</code> and <code>registerAllKeys</code> methods have the option to populate the cache with the registration results from the server. The <code>registerRegex</code> and <code>registerAllKeys</code> methods can also optionally return the current list of keys registered on the server.</p>
+<p>The <code>RegisterKeys</code>, <code>RegisterRegex</code> and <code>RegisterAllKeys</code> methods have the option to populate the cache with the registration results from the server. The <code>RegisterRegex</code> and <code>RegisterAllKeys</code> methods can also optionally return the current list of keys registered on the server.</p>
<h2 id="setting-up-client-notification"><a id="registering-interest-for-entries__section_C1A3F89EE73448D7AFF2076F41848F55" class="no-quick-link"></a>Setting Up Client Notification</h2>
-<p>In addition to the programmatic function calls, to register interest for a server region and receive updated entries you need to configure the region with the <code>PROXY</code> or <code>CACHING_PROXY RegionShortcut</code> setting. The region’s pool should have <code>subscription-enabled=true</code> set either in the client XML or programmatically via a <code>CacheFactory::setSubscriptionEnabled(true)</code> API call. Otherwise, when you register interest, you will get an <code> [...]
+<p>In addition to the programmatic function calls, to register interest for a server region and receive updated entries you need to configure the region with the <code>PROXY</code> or <code>CACHING_PROXY RegionShortcut</code> setting. The region’s pool should have <code>subscription-enabled=true</code> set either in the client XML or programmatically via a <code>CacheFactory::SetSubscriptionEnabled(true)</code> API call. Otherwise, when you register interest, you will get an <code> [...]
<pre class="highlight plaintext"><code><region name="listenerWriterLoader" refid="CACHING_PROXY">
...
</code></pre>
@@ -267,48 +267,48 @@ limitations under the License.
<p><strong>Notification Sequence</strong></p>
-<p>Notifications invoke <code>CacheListeners</code> of cacheless clients in all cases for keys that have been registered on the server. Similarly, invalidates received from the server invoke <code>CacheListeners</code> of cacheless clients.</p>
+<p>Notifications invoke <code>CacheListeners</code> of cacheless clients in all cases for keys that have been registered on the server. Similarly, Invalidate events received from the server invoke <code>CacheListeners</code> of cacheless clients.</p>
-<p>If you register to receive notifications, listener callbacks are invoked irrespective of whether the key is in the client cache when a <code>destroy</code> or <code>invalidate</code> event is received.</p>
+<p>If you register to receive notifications, listener callbacks are invoked irrespective of whether the key is in the client cache when a <code>Destroy</code> or <code>Invalidate</code> event is received.</p>
<h2 id="registering-interest-for-specific-keys"><a id="registering-interest-for-entries__section_8772147940754C2D9688C789EB2F2AA6" class="no-quick-link"></a>Registering Interest for Specific Keys</h2>
-<p>You register and unregister interest for specific keys through the <code>registerKeys</code> and <code>unregisterKeys</code> functions. You register interest in a key or set of keys by specifying the key name using the programmatic syntax shown in the following example:</p>
+<p>You register and unregister interest for specific keys through the <code>RegisterKeys</code> and <code>UnregisterKeys</code> functions. You register interest in a key or set of keys by specifying the key name using the programmatic syntax shown in the following example:</p>
<pre class="highlight plaintext"><code>keys0.push_back(keyPtr1);
keys1.push_back(keyPtr3);
-regPtr0->registerKeys(keys0);
-regPtr1->registerKeys(keys1);
+regPtr0->RegisterKeys(keys0);
+regPtr1->RegisterKeys(keys1);
</code></pre>
<p>The programmatic code snippet in the next example shows how to unregister interest in specific keys:</p>
-<pre class="highlight plaintext"><code>regPtr0->unregisterKeys(keys0);
-regPtr1->unregisterKeys(keys1);
+<pre class="highlight plaintext"><code>regPtr0->UnregisterKeys(keys0);
+regPtr1->UnregisterKeys(keys1);
</code></pre>
<h2 id="registering-interest-for-all-keys"><a id="registering-interest-for-entries__section_EA4525CCDC474DD495410E948EAF566C" class="no-quick-link"></a>Registering Interest for All Keys</h2>
<p>If the client registers interest in all keys, the server provides notifications for all updates to all keys in the region. The next example shows how to register interest in all keys:</p>
-<pre class="highlight plaintext"><code>regPtr0->registerAllKeys();
-regPtr1->registerAllKeys();
+<pre class="highlight plaintext"><code>regPtr0->RegisterAllKeys();
+regPtr1->RegisterAllKeys();
</code></pre>
<p>The following example shows a code sample for unregistering interest in all keys.</p>
-<pre class="highlight plaintext"><code>regPtr0->unregisterAllKeys();
-regPtr1->unregisterAllKeys();
+<pre class="highlight plaintext"><code>regPtr0->UnregisterAllKeys();
+regPtr1->UnregisterAllKeys();
</code></pre>
<h2 id="registering-interest-using-regular-expressions"><a id="registering-interest-for-entries__section_BD50B80FCE9F429C8F6A9FEA818D5A91" class="no-quick-link"></a>Registering Interest Using Regular Expressions</h2>
-<p>The <code>registerRegex</code> function registers interest in a regular expression pattern. The server automatically sends the client changes for entries whose keys match the specified pattern.</p>
+<p>The <code>RegisterRegex</code> function registers interest in a regular expression pattern. The server automatically sends the client changes for entries whose keys match the specified pattern.</p>
<p><em>Keys must be strings in order to register interest using regular expressions.</em></p>
<p>The following example shows interest registration for all keys whose first four characters are <code>Key-</code>, followed by any string of characters. The characters <code>.*</code> represent a wildcard that matches any string.</p>
-<pre class="highlight plaintext"><code>regPtr1->registerRegex("Key-.*");
+<pre class="highlight plaintext"><code>regPtr1->RegisterRegex("Key-.*");
</code></pre>
-<p>To unregister interest using regular expressions, you use the <code>unregisterRegex</code> function. The next example shows how to unregister interest in all keys whose first four characters are <code>Key-</code>, followed by any string (represented by the <code>.*</code> wildcard).</p>
-<pre class="highlight plaintext"><code>regPtr1->unregisterRegex("Key-.*");
+<p>To unregister interest using regular expressions, you use the <code>UnregisterRegex</code> function. The next example shows how to unregister interest in all keys whose first four characters are <code>Key-</code>, followed by any string (represented by the <code>.*</code> wildcard).</p>
+<pre class="highlight plaintext"><code>regPtr1->UnregisterRegex("Key-.*");
</code></pre>
<h2 id="register-interest-scenario"><a id="registering-interest-for-entries__section_2D71A423B185493489129AAC30DC6733" class="no-quick-link"></a>Register Interest Scenario</h2>
@@ -348,7 +348,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/remote-queries.html b/docs/geode-native/dotnet/112/remote-queries.html
index fa95067..c6635e4 100644
--- a/docs/geode-native/dotnet/112/remote-queries.html
+++ b/docs/geode-native/dotnet/112/remote-queries.html
@@ -267,6 +267,9 @@ You can optimize your queries by defining indexes on the cache server.</p>
<p>Querying and indexing operate only on remote cache server contents.</p>
+<p><strong>Note:</strong> Because floating point numbers can not reliably be compared for equality, do not use
+floating point values as keys or key components when constructing a query.</p>
+
<h3 id="query-language:-oql"><a id="QueryLanguage"></a>Query language: OQL</h3>
<p>Geode provides a SQL-like querying language called OQL that allows you to access data stored in Geode regions.
@@ -311,7 +314,7 @@ managing the compilation and execution of queries, and for retrieving an existin
<ol>
<li> Create an instance of the <code>QueryService</code> class. If you are using the pool API (recommended), you should obtain the <code>QueryService</code> from the pool.</li>
<li> Create a <code>Query</code> instance that is compatible with the OQL specification.</li>
-<li> Use the <code>Query.execute()</code> method to submit the query string to the cache server. The server
+<li> Use the <code>Query.Execute()</code> method to submit the query string to the cache server. The server
remotely evaluates the query string and returns the results to the client.</li>
<li> Iterate through the returned objects.</li>
</ol>
@@ -369,7 +372,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/security/authentication.html b/docs/geode-native/dotnet/112/security/authentication.html
index 53858ff..c5314d9 100644
--- a/docs/geode-native/dotnet/112/security/authentication.html
+++ b/docs/geode-native/dotnet/112/security/authentication.html
@@ -318,7 +318,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/security/security-systemprops.html b/docs/geode-native/dotnet/112/security/security-systemprops.html
deleted file mode 100644
index c55ed29..0000000
--- a/docs/geode-native/dotnet/112/security/security-systemprops.html
+++ /dev/null
@@ -1,324 +0,0 @@
-<!doctype html>
-<html>
-<head>
- <meta charset="utf-8">
- <!-- Always force latest IE rendering engine or request Chrome Frame -->
- <meta content="IE=edge,chrome=1" http-equiv="X-UA-Compatible">
-
-
- <link href='https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,300italic,400italic,400,600' rel='stylesheet' type='text/css'>
- <!-- Use title if it's in the page YAML frontmatter -->
- <title>
- Security-Related System Properties |
- Geode Native .NET Docs
- </title>
- <meta name="viewport" content="width=device-width, initial-scale=1.0">
- <link href="/stylesheets/all.css" rel="stylesheet" media="screen, print" />
- <link href="/stylesheets/print.css" rel="stylesheet" media="print" />
- <link href='/images/favicon.ico' rel='shortcut icon'>
-
- <script src="/javascripts/all.js"></script>
-
-</head>
-
-<body class="docs docs_geode-native docs_geode-native_dotnet docs_geode-native_dotnet_112 docs_geode-native_dotnet_112_security docs_geode-native_dotnet_112_security_security-systemprops has-subnav">
-
-<div class="viewport">
- <div class='wrap'>
- <script type="text/javascript">
- document.domain = "apache.org";
- </script>
-
- <!--
-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.
--->
-<header class="header header-layout">
- <h1 class="logo">
- <a href="/">
- <img src="/images/Apache_Geode_logo_symbol_white.png" style="width:30px;">
- Apache Geode Native .NET Documentation
- </a>
- </h1>
- <div class="header-links js-bar-links">
- <div class="btn-menu" data-behavior="MenuMobile"></div>
- <div class="header-item"><a href="http://geode.apache.org">Back to Product Page</a></div>
- <div class="header-item">
- <a href="http://geode.apache.org/community" target="_blank">Community</a>
- </div>
- </div>
-</header>
-
-
- <div class="container">
-
- <!--googleoff: index-->
- <!--
-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.
--->
-<div id="sub-nav" class="js-sidenav nav-container" role="navigation">
-<a class="sidenav-title" data-behavior="SubMenuMobile">Doc Index</a>
- <div class="nav-content">
- <ul>
- <li>
- <a href="/docs/geode-native/dotnet/112/about-client-users-guide.html">Apache Geode Native Documentation</a>
- </li>
- <li class="has_submenu">
- <a href="/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html">Getting Started with the Native Library</a>
- <ul>
- <li>
- <a href="/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html#set_up_dev_environment">Set Up Your Development Environment</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html#establish_cluster_access">Establish Access to a Geode Cluster</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html#app_dev_walkthroughs">Application Development Walkthroughs</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/getting-started/getting-started-nc-client.html#programming_examples">Programming Examples</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/getting-started/put-get-example.html">Put/Get/Remove Examples</a>
- </li>
- </ul>
- </li>
- <li class="has_submenu">
- <a href="/docs/geode-native/dotnet/112/configuring/configuration.html">Configuring a Client Application</a>
- <ul>
- <li>
- <a href="/docs/geode-native/dotnet/112/configuring/system-level-configuration.html">System Level Configuration</a>
- </li>
- </ul>
- </li>
-
- <li>
- <a href="/docs/geode-native/dotnet/112/configuring/config-client-cache.html">Configuring the Client Cache</a>
- </li>
- <li class="has_submenu">
- <a href="/docs/geode-native/dotnet/112/regions/regions.html">Configuring Regions</a>
- <ul>
- <li>
- <a href="/docs/geode-native/dotnet/112/regions/registering-interest-for-entries.html">Registering Interest for Entries</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/regions/region-attributes.html">Region Attributes</a>
- </li>
- </ul>
- </li>
-
- <li>
- <a href="/docs/geode-native/dotnet/112/serialization/data-serialization.html">Serializing Data</a>
- </li>
-
- <li>
- <a href="/docs/geode-native/dotnet/112/remote-queries.html">Remote Queries</a>
- </li>
-
- <li>
- <a href="/docs/geode-native/dotnet/112/continuous-queries.html">Continuous Queries</a>
- </li>
-
- <li class="has_submenu">
- <a href="/docs/geode-native/dotnet/112/security/security.html">Security: Authentication and Encryption</a>
- <ul>
- <li>
- <a href="/docs/geode-native/dotnet/112/security/authentication.html">Authentication</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/security/sslclientserver.html">TLS/SSL Client-Server Communication Encryption</a>
- </li>
- </ul>
- </li>
-
- <li>
- <a href="/docs/geode-native/dotnet/112/function-execution.html">Function Execution</a>
- </li>
-
- <li>
- <a href="/docs/geode-native/dotnet/112/transactions.html">Transactions</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/configuring/sysprops.html">System Properties</a>
- </li>
- <li>
- <a href="/docs/geode-native/dotnet/112/client-cache-ref.html">Client Cache XML Reference</a>
- </li>
- </ul>
- </div>
-</div>
-
- <!--googleon: index-->
-
- <main class="content content-layout" id="js-content" role="main">
- <a id="top"></a>
- <!--
-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.
--->
-<span style="font-weight:200;font-size:31px;" style="float:left;">
- <img src="/images/Apache_Geode_logo_symbol.png" style="height:26px;">
- Apache Geode Native .NET
-</span>
- <span class="local-header version-info" style="float:right;">
- <a href="https://cwiki.apache.org/confluence/display/GEODE/Release+Notes">CHANGELOG</a>
- </span>
-
- <!--
-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.
--->
- <h1 class="title-container" >
- Security-Related System Properties
- </h1>
-
- <div id="js-quick-links" >
-
- </div>
- <div class="to-top" id="js-to-top">
- <a href="#top" title="back to top"></a>
- </div>
- <!--
-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.
--->
-
-<p>The table describes the security-related system properties in the <code>geode.properties</code> file for native client authentication and authorization.</p>
-
-<p><a id="security__section_6DC4C72A2EEB432AA40DE97D438FD1E7"></a><a id="security__table_92A6A66523764199A19BCD66BA189921"></a></p>
-
-<table>
-<caption><span class="tablecap">System Properties for Client Authentication and Authorization</span></caption>
-<colgroup>
-<col width="50%" />
-<col width="50%" />
-</colgroup>
-<tbody>
-<tr class="odd">
-<td><code class="ph codeph">security-client-dhalgo</code></td>
-<td>Diffie-Hellman based credentials encryption is not supported.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">security-client-kspath</code></td>
-<td>Path to a .pem file, which contains the public certificates for all Geode cache servers to which the client can connect through specified endpoints.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">ssl-enabled</code></td>
-<td>True if SSL connection support is enabled.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">ssl-keystore</code></td>
-<td>Name of the .pem keystore file, containing the client’s private key. Not set by default. Required if <code class="ph codeph">ssl-enabled</code> is true.</td>
-</tr>
-<tr class="odd">
-<td><code class="ph codeph">ssl-keystore-password</code></td>
-<td>Sets the password for the private key PEM file for SSL.</td>
-</tr>
-<tr class="even">
-<td><code class="ph codeph">ssl-truststore</code></td>
-<td><p>Name of the .pem truststore file, containing the servers’ public certificate. Not set by default. Required if <code class="ph codeph">ssl-enabled</code> is true</p></td>
-</tr>
-</tbody>
-</table>
-
-
-
- </main>
- </div>
- </div>
-</div>
-
-<div id="scrim"></div>
-
-<div class="container">
- <footer class="site-footer-links">
- <!--
-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.
--->
-<div class="copyright">
- <a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
-</div>
-<div class="support">
- Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
-</div>
-
- </footer>
-</div><!--end of container-->
-
-</body>
-</html>
diff --git a/docs/geode-native/dotnet/112/security/security.html b/docs/geode-native/dotnet/112/security/security.html
index 98af7cd..c0432bf 100644
--- a/docs/geode-native/dotnet/112/security/security.html
+++ b/docs/geode-native/dotnet/112/security/security.html
@@ -291,7 +291,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/security/sslclientserver.html b/docs/geode-native/dotnet/112/security/sslclientserver.html
index 77619df..477b8f9 100644
--- a/docs/geode-native/dotnet/112/security/sslclientserver.html
+++ b/docs/geode-native/dotnet/112/security/sslclientserver.html
@@ -274,7 +274,7 @@ When configuring TLS/SSL security for your client, you may find it helpful to re
must be able to communicate with both locator and server components.</p></li>
<li><p>On the client, set <code>ssl-enabled</code> to <code>true</code>. </p></li>
<li><p>On the client, set <code>ssl-keystore</code> and <code>ssl-truststore</code> to point to your keystore files. Paths to the keystore and truststore are local to the client.
-See <a href="/docs/geode-native/dotnet/112/security/security-systemprops.html#security">Security-Related System Properties</a> for a description of these properties.</p></li>
+See <a href="/docs/geode-native/dotnet/112/configuring/sysprops.html#attributes-gfcpp__table_security_props">Security Properties</a> for a description of these properties.</p></li>
</ol>
<h1 id="starting-and-stopping-the-client-and-server-with-ssl-in-place">Starting and stopping the client and server with SSL in place</h1>
@@ -347,7 +347,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/data-serialization.html b/docs/geode-native/dotnet/112/serialization/data-serialization.html
index bb93e47..733b154 100644
--- a/docs/geode-native/dotnet/112/serialization/data-serialization.html
+++ b/docs/geode-native/dotnet/112/serialization/data-serialization.html
@@ -434,7 +434,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/custom-class-igfserializable.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/custom-class-igfserializable.html
index f3b7b38..2e2c74b 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/custom-class-igfserializable.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/custom-class-igfserializable.html
@@ -402,7 +402,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization-options.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization-options.html
index 7e54b19..bc24c68 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization-options.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization-options.html
@@ -329,7 +329,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization.html
index 512bd97..ecf5d4d 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-data-serialization.html
@@ -310,7 +310,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
index 9c2c4fb..23ab94b 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
@@ -322,7 +322,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization-features.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization-features.html
index e109678..77048e5 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization-features.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization-features.html
@@ -297,7 +297,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization.html
index 081bbdc..9c80934 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/dotnet-pdx-serialization.html
@@ -290,7 +290,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/extending-pdx-autoserializer.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/extending-pdx-autoserializer.html
index 10a7ed0..64ed827 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/extending-pdx-autoserializer.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/extending-pdx-autoserializer.html
@@ -325,7 +325,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/how-igfserializable-works.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/how-igfserializable-works.html
index 50022c7..665c657 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/how-igfserializable-works.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/how-igfserializable-works.html
@@ -291,7 +291,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/implementing-igfserializable.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/implementing-igfserializable.html
index 8c9512b..8a34431 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/implementing-igfserializable.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/implementing-igfserializable.html
@@ -382,7 +382,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/mapping-dotnet-domain-type-names.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/mapping-dotnet-domain-type-names.html
index 8abdf58..31745f4 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/mapping-dotnet-domain-type-names.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/mapping-dotnet-domain-type-names.html
@@ -291,7 +291,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/programming-ipdxinstance.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/programming-ipdxinstance.html
index 0331c8b..f2dd342 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/programming-ipdxinstance.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/programming-ipdxinstance.html
@@ -312,7 +312,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/registering-the-type.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/registering-the-type.html
index 15395cf..7bbe49f 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/registering-the-type.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/registering-the-type.html
@@ -295,7 +295,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializable-types.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializable-types.html
index 1f8b73d..6968909 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializable-types.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializable-types.html
@@ -288,7 +288,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-igfserializable.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-igfserializable.html
index 0d24b7f..8c41f72 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-igfserializable.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-igfserializable.html
@@ -290,7 +290,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-ipdxserializable.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
index 1a9e0b3..d7fe739 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
@@ -261,7 +261,7 @@ limitations under the License.
<ol>
<li> Write your domain class’s standard .NET data fields using the <code>IPdxWriter</code> write methods. Geode automatically provides <code>IPdxWriter</code> to the <code>ToData</code> function for <code>IPdxSerializable</code> objects.</li>
-<li><p>Call the <code>ToData markIdentifyField</code> function for each field Geode should use to identify your object. This is used to compare objects for operations like <code>DISTINCT</code> queries. The <code>markIdentifyField</code> call must come after the associated field write methods.</p>
+<li><p>Call the <code>ToData MarkIdentifyField</code> function for each field Geode should use to identify your object. This is used to compare objects for operations like <code>DISTINCT</code> queries. The <code>MarkIdentifyField</code> call must come after the associated field write methods.</p>
<p>Example:</p>
<pre class="highlight plaintext"><code>// object fields
@@ -334,7 +334,7 @@ public void ToData(IPdxWriter writer)
m_arrayZeroSize = reader.ReadByteArray("arrayZeroSize");
}
</code></pre></li>
-<li><p>Optionally, program your domain object’s equals and hashcode methods.</p></li>
+<li><p>Optionally, program your domain object’s <code>Equals</code> and <code>Hashcode</code> methods.</p></li>
</ol>
@@ -366,7 +366,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializing-domain-objects.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializing-domain-objects.html
index 34b4140..2df88e0 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializing-domain-objects.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/serializing-domain-objects.html
@@ -295,7 +295,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/using-ipdxinstancefactory.html b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/using-ipdxinstancefactory.html
index 215b9c9..4627802 100644
--- a/docs/geode-native/dotnet/112/serialization/dotnet-serialization/using-ipdxinstancefactory.html
+++ b/docs/geode-native/dotnet/112/serialization/dotnet-serialization/using-ipdxinstancefactory.html
@@ -277,7 +277,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/112/transactions.html b/docs/geode-native/dotnet/112/transactions.html
index 94dc7c1..58403d0 100644
--- a/docs/geode-native/dotnet/112/transactions.html
+++ b/docs/geode-native/dotnet/112/transactions.html
@@ -257,8 +257,8 @@ For complete information about how transactions are conducted on the Geode serve
<h2 id="native-client-transaction-apis"><a id="client-transaction-apis"></a>Native Client Transaction APIs</h2>
-<p>The API for distributed transactions has the familiar relational database methods, <code>begin</code>,
-<code>commit</code>, and <code>rollback</code>. There are also APIs available to suspend and resume transactions.</p>
+<p>The API for distributed transactions has the familiar relational database methods, <code>Begin</code>,
+<code>Commit</code>, and <code>Rollback</code>. There are also APIs available to suspend and resume transactions.</p>
<p>The .NET classes for executing transactions are:</p>
@@ -273,7 +273,7 @@ For complete information about how transactions are conducted on the Geode serve
a client performs a transaction, the transaction is delegated to a server that brokers the
transaction.</p>
-<p>Start each transaction with a <code>begin</code> operation, and end the transaction with a <code>commit</code> or a <code>rollback</code>.</p>
+<p>Start each transaction with a <code>Begin</code> operation, and end the transaction with a <code>Commit</code> or a <code>Rollback</code>.</p>
<p>To maintain cache consistency, the local client cache is not used during a transaction.
When the transaction completes or is suspended, local cache usage is reinstated.</p>
@@ -340,7 +340,7 @@ For the complete source, see the example source directory.</p>
<p>Within the transaction, the client populates data store with 10 values associated with Key1 - Key10.</p>
<pre class="highlight csharp"><code> <span class="k">foreach</span><span class="p">(</span><span class="kt">var</span> <span class="n">key</span> <span class="k">in</span> <span class="n">keys</span><span class="p">)</span>
<span class="p">{</span>
- <span class="kt">var</span> <span class="k">value</span> <span class="p">=</span> <span class="nf">getValueFromExternalSystem</span><span class="p">();</span>
+ <span class="kt">var</span> <span class="k">value</span> <span class="p">=</span> <span class="nf">GetValueFromExternalSystem</span><span class="p">();</span>
<span class="n">region</span><span class="p">.</span><span class="nf">Put</span><span class="p">(</span><span class="n">key</span><span class="p">,</span> <span class="k">value</span><span class="p">);</span>
<span class="p">}</span>
</code></pre>
@@ -392,7 +392,7 @@ limitations under the License.
-->
<div class="copyright">
<a href='/'>Apache Geode Documentation</a>
- © 2020 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
+ © 2021 <a href='http://www.apache.org/'>The Apache Software Foundation</a>.
</div>
<div class="support">
Need help? <a href="http://geode.apache.org/community" target="_blank">Visit the Community</a>
diff --git a/docs/geode-native/dotnet/113/continuous-queries.html b/docs/geode-native/dotnet/113/continuous-queries.html
index 8c2ddb1..770e64f 100644
--- a/docs/geode-native/dotnet/113/continuous-queries.html
+++ b/docs/geode-native/dotnet/113/continuous-queries.html
@@ -290,18 +290,21 @@ Compare this to register interest by reviewing <a href="/docs/geode-native/dotne
<li><p><strong>Active query execution</strong>. Once initialized, the queries operate on new events. Events that change the query result are sent to the client immediately.</p></li>
</ul>
+<p><strong>Note:</strong> Because floating point numbers can not reliably be compared for equality, do not use
+floating point values as keys or key components when constructing a query.</p>
+
<h2 id="typical-continuous-query-lifecycle"><a id="cq_api"></a>Typical Continuous Query Lifecycle</h2>
<ol>
<li> The client creates the CQ. This sets up everything for running the query and provides the client with a <code>CqQuery</code> object, but does not execute the CQ. At this point, the query is in a <code>STOPPED</code>state, ready to be closed or run.</li>
-<li><p>The client initiates the CQ with an API call to one of the <code>CqQuery execute*</code> methods. This puts the query into a <code>RUNNING</code> state on the client and on the server. The server remotely evaluates the query string, and optionally returns the results to the client. <code>CqQuery execute*</code> methods include:</p>
+<li><p>The client initiates the CQ with an API call to one of the <code>CqQuery Execute*</code> methods. This puts the query into a <code>RUNNING</code> state on the client and on the server. The server remotely evaluates the query string, and optionally returns the results to the client. <code>CqQuery Execute*</code> methods include:</p>
<ul>
<li><code>CqQuery.Execute()</code></li>
<li><code>CqQuery.ExecuteWithInitialResults()</code></li>
</ul></li>
<li><p>A CQ Listener waits for events. When it receives events, it takes action accordingly with the data in the CqEvent.</p></li>
-<li><p>The CQ is closed by a client call to <code>CqQuery.close</code>. This de-allocates all resources in use for the CQ on the client and server. At this point, the cycle could begin again with the creation of a new <code>CqQuery</code> instance.</p></li>
+<li><p>The CQ is closed by a client call to <code>CqQuery.Close</code>. This de-allocates all resources in use for the CQ on the client and server. At this point, the cycle could begin again with the creation of a new <code>CqQuery</code> instance.</p></li>
</ol>
<h2 id="executing-a-continuous-query-from-the-client"><a id="ExecutingACQ"></a>Executing a Continuous Query from the Client</h2>
@@ -311,7 +314,7 @@ Compare this to register interest by reviewing <a href="/docs/geode-native/dotne
<ol>
<li> Create an instance of the <code>QueryService</code> class. If you are using the pool API (recommended), you should obtain the <code>QueryService</code> from the pool.</li>
<li> Define a CQ Listener (an <code>ICqListener</code>) to field events sent from the server.</li>
-<li> Use one of the <code>CqQuery execute*</code> methods to submit the query string to the cache server.</li>
+<li> Use one of the <code>CqQuery Execute*</code> methods to submit the query string to the cache server.</li>
<li> The server remotely evaluates the query string, then monitors those results and notifies the client if they change.</li>
<li> The client listens for changes that match the query predicate.</li>
<li> Iterate through the returned objects.</li>
diff --git a/docs/geode-native/dotnet/113/function-execution.html b/docs/geode-native/dotnet/113/function-execution.html
index 88e657b..76a0872 100644
--- a/docs/geode-native/dotnet/113/function-execution.html
+++ b/docs/geode-native/dotnet/113/function-execution.html
@@ -289,36 +289,36 @@ in the Geode User Guide for details on how to write and register server-resident
<h2 id="how-functions-execute"><a id="nc-fe-how_functions_execute"></a>How Functions Execute</h2>
<ol>
-<li> The calling client application runs the <code>execute</code> method on the <code>Execution</code> object. The function must already be registered on the servers.</li>
-<li> The function is invoked on the servers where it needs to run. The servers are determined by the <code>FunctionService on*</code>
+<li> The calling client application runs the <code>Execute</code> method on the <code>Execution</code> object. The function must already be registered on the servers.</li>
+<li> The function is invoked on the servers where it needs to run. The servers are determined by the <code>FunctionService On*</code>
method calls, region configuration, and any filters.</li>
<li> If the function has results, the result is returned in a <code>ResultCollector</code> object.</li>
-<li> The client collects results using the <code>ResultCollector.getResult()</code> method.</li>
+<li> The client collects results using the <code>ResultCollector.GetResult()</code> method.</li>
</ol>
<p>In every client where you want to execute the function and process the results:</p>
<ul>
-<li>Use one of the <code>FunctionService on*</code> methods to create an <code>Execution</code> object. The <code>on*</code> methods,
-<code>onRegion</code>, <code>onServer</code> and <code>onServers</code>, define the highest level where the function is run.</li>
-<li>If you use <code>onRegion</code> you can further narrow your run scope by setting key filters.</li>
-<li>A function run using <code>onRegion</code> is a <em>data dependent</em> function – others are <em>data-independent</em> functions.</li>
+<li>Use one of the <code>FunctionService On*</code> methods to create an <code>Execution</code> object. The <code>On*</code> methods,
+<code>OnRegion</code>, <code>OnServer</code> and <code>OnServers</code>, define the highest level where the function is run.</li>
+<li>If you use <code>OnRegion</code> you can further narrow your run scope by setting key filters.</li>
+<li>A function run using <code>OnRegion</code> is a <em>data dependent</em> function – others are <em>data-independent</em> functions.</li>
<li><p>You can run a data dependent function against partitioned and colocated partitioned regions. From the client, provide the appropriate key
sets to the function call.</p></li>
<li><p>The <code>Execution</code> object allows you to customize the invocation by:</p>
<ul>
-<li> Providing a set of data keys to <code>withFilter</code> to narrow the execution scope. This works only for <code>onRegion</code> Execution objects (data-dependent functions).</li>
-<li> Providing function arguments to <code>withArgs</code>.</li>
-<li> Defining a custom <code>ResultCollector</code> for <code>withCollector</code>.</li>
+<li> Providing a set of data keys to <code>WithFilter</code> to narrow the execution scope. This works only for <code>OnRegion</code> Execution objects (data-dependent functions).</li>
+<li> Providing function arguments to <code>WithArgs</code>.</li>
+<li> Defining a custom <code>ResultCollector</code> for <code>WithCollector</code>.</li>
</ul></li>
-<li><p>Call the <code>Execution.execute()</code> method to run the function.</p></li>
+<li><p>Call the <code>Execution.Execute()</code> method to run the function.</p></li>
</ul>
<h2 id="processing-function-results"><a id="nc-fe-processing_function_results"></a>Processing Function Results</h2>
<p>To get the results from the function in the client app, use the result collector returned from the function execution.
-The <code>getResult</code> methods of the default result collector block until all results are received, then return the full result set.</p>
+The <code>GetResult</code> methods of the default result collector block until all results are received, then return the full result set.</p>
<p>The client can use the default result collector. If the client needs special results handling, code a custom <code>ResultsCollector</code> implementation to replace the default.
Use the <code>Execution::withCollector</code> method to specify the custom collector.
@@ -328,12 +328,12 @@ To handle the results in a custom manner:</p>
<li> Write a class that implements the <code>ResultCollector</code> interface to handle the results in a custom manner. The methods are of two types: one handles data and information from Geode and populates the results set, while the other returns the compiled results to the calling application:
<ul>
-<li> <code>addResult</code> is called when results arrive from the <code>Function</code> methods. Use <code>addResult</code> to add a single result to the ResultCollector.</li>
-<li> <code>endResults</code> is called to signal the end of all results from the function execution.</li>
-<li> <code>getResult</code> is available to your executing application (the one that calls <code>Execution.execute</code>) to retrieve the results. This may block until all results are available.</li>
-<li> <code>clearResults</code> is called to clear partial results from the results collector. This is used only for highly available <code>onRegion</code> functions where the calling application waits for the results. If the call fails, before Geode retries the execution, it calls <code>clearResults</code> to ready the instance for a clean set of results.</li>
+<li> <code>AddResult</code> is called when results arrive from the <code>Function</code> methods. Use <code>AddResult</code> to add a single result to the ResultCollector.</li>
+<li> <code>EndResults</code> is called to signal the end of all results from the function execution.</li>
+<li> <code>GetResult</code> is available to your executing application (the one that calls <code>Execution.Execute</code>) to retrieve the results. This may block until all results are available.</li>
+<li> <code>ClearResults</code> is called to clear partial results from the results collector. This is used only for highly available <code>OnRegion</code> functions where the calling application waits for the results. If the call fails, before Geode retries the execution, it calls <code>ClearResults</code> to ready the instance for a clean set of results.</li>
</ul></li>
-<li> Use the <code>Execution</code> object in your executing member to call <code>withCollector</code>, passing your custom collector.</li>
+<li> Use the <code>Execution</code> object in your executing member to call <code>WithCollector</code>, passing your custom collector.</li>
</ol>
<h2 id="function-execution-example"><a id="nc-fe-examples"></a>Function Execution Example</h2>
@@ -345,7 +345,7 @@ To handle the results in a custom manner:</p>
<li>The function is preloaded with a JAR file containing the server-side Java function code. </li>
<li>The function, called “ExampleMultiGetFunction”, is defined in the
<code>examples/utilities</code> directory of your distribution. As its input parameter, the function takes an array of keys,
-then performs a <code>get</code> on each key and returns an array containing the results.</li>
+then performs a <code>Get</code> on each key and returns an array containing the results.</li>
<li>The function does not load values into the data store. That is a separate operation, performed in these examples by
the client, and does not involve the server-side function.</li>
</ul>
@@ -362,7 +362,7 @@ of the input parameter and return value.</p>
</ul>
<p>If the client expects results, it must create a result object.
-The .NET example uses a built-in result collector (<code>IResultCollector.getResults()</code>) to retrieve the function results.</p>
+The .NET example uses a built-in result collector (<code>IResultCollector.GetResults()</code>) to retrieve the function results.</p>
<h3 id=".net-example"><a id="nc-fe-dotnet_example"></a>.NET Example</h3>
diff --git a/docs/geode-native/dotnet/113/preserving-data/config-durable-interest-keys.html b/docs/geode-native/dotnet/113/preserving-data/config-durable-interest-keys.html
index fbc0a81..b3ac086 100644
--- a/docs/geode-native/dotnet/113/preserving-data/config-durable-interest-keys.html
+++ b/docs/geode-native/dotnet/113/preserving-data/config-durable-interest-keys.html
@@ -9,7 +9,6 @@
<link href='https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,300italic,400italic,400,600' rel='stylesheet' type='text/css'>
<!-- Use title if it's in the page YAML frontmatter -->
<title>
- Configuring Durable Interest in Keys |
Geode Native .NET Docs
</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -233,9 +232,6 @@ 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.
-->
- <h1 class="title-container" >
- Configuring Durable Interest in Keys
- </h1>
<div id="js-quick-links" >
@@ -243,7 +239,11 @@ limitations under the License.
<div class="to-top" id="js-to-top">
<a href="#top" title="back to top"></a>
</div>
- <!--
+ <p>–</p>
+
+<h2 id="title:-configuring-durable-interest-in-keys">title: Configuring Durable Interest in Keys</h2>
+
+<!--
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.
@@ -266,7 +266,7 @@ limitations under the License.
<p>You still register interest for other keys, but not durable interest. When the client is connected to its servers, it receives messages for those non-durable keys. When the client is disconnected, its non-durable interest registrations are deleted but messages that are already in the queue remain there.</p>
-<p>For durable clients, all interest registration is done immediately after the regions are created. This is required whether interest registration is durable or not durable. An extra <code>registerInterest</code> parameter specified for durable clients indicates whether the registration is durable (true) or not (false).</p>
+<p>For durable clients, all interest registration is done immediately after the regions are created. This is required whether interest registration is durable or not durable. An extra <code>RegisterInterest</code> parameter specified for durable clients indicates whether the registration is durable (true) or not (false).</p>
<h2 id="api-client-durable-interest-list-registration-(c++)">API Client Durable Interest List Registration (C++)</h2>
@@ -275,7 +275,7 @@ limitations under the License.
// durable (true) or nondurable(default).
VectorOfCacheableKey keys;
keys.push_back( CacheableString::create("Key-1") );
-regionPtr->registerKeys(keys,true);
+regionPtr->RegisterKeys(keys,true);
</code></pre>
<p><a id="concept_6456354A9AD945C780A5AA864B41B564__section_3DE5872B0888410EB42D52CFB28C79E5"></a>
diff --git a/docs/geode-native/dotnet/113/regions/registering-interest-for-entries.html b/docs/geode-native/dotnet/113/regions/registering-interest-for-entries.html
index 19baf5a..c87f37d 100644
--- a/docs/geode-native/dotnet/113/regions/registering-interest-for-entries.html
+++ b/docs/geode-native/dotnet/113/regions/registering-interest-for-entries.html
@@ -264,17 +264,17 @@ limitations under the License.
<p>You can register interest for specific entry keys or for all keys. Regular expressions can be used to register interest for keys whose strings match the expression. You can also unregister interest for specific keys, groups of keys based on regular expressions, or for all keys.</p>
-<p><strong>Note:</strong> Interest registration and unregistration are symmetrical operations. Consequently, you cannot register interest in all keys and then unregister interest in a specific set of keys. Also, if you first register interest in specific keys with <code>registerKeys</code>, then call <code>registerAllKeys</code>, you must call <code>unregisterAllKeys</code> before specifying interest in specific keys again.</p>
+<p><strong>Note:</strong> Interest registration and unregistration are symmetrical operations. Consequently, you cannot register interest in all keys and then unregister interest in a specific set of keys. Also, if you first register interest in specific keys with <code>RegisterKeys</code>, then call <code>RegisterAllKeys</code>, you must call <code>UnregisterAllKeys</code> before specifying interest in specific keys again.</p>
<h2 id="client-api-for-registering-interest"><a id="registering-interest-for-entries__section_C9A3D7F193B24ACD83B2D67813E596A0" class="no-quick-link"></a>Client API for Registering Interest</h2>
<p>You register client interest through the .NET API. The .NET API provides the <code>RegisterKeys</code>, <code>RegisterAllKeys</code>, and <code>RegisterRegex</code> methods, with corresponding unregistration accomplished using the <code>UnregisterKeys</code>, <code>UnregisterAllKeys</code>, and <code>UnregisterRegex</code> methods.</p>
-<p>The <code>registerKeys</code>, <code>registerRegex</code> and <code>registerAllKeys</code> methods have the option to populate the cache with the registration results from the server. The <code>registerRegex</code> and <code>registerAllKeys</code> methods can also optionally return the current list of keys registered on the server.</p>
+<p>The <code>RegisterKeys</code>, <code>RegisterRegex</code> and <code>RegisterAllKeys</code> methods have the option to populate the cache with the registration results from the server. The <code>RegisterRegex</code> and <code>RegisterAllKeys</code> methods can also optionally return the current list of keys registered on the server.</p>
<h2 id="setting-up-client-notification"><a id="registering-interest-for-entries__section_C1A3F89EE73448D7AFF2076F41848F55" class="no-quick-link"></a>Setting Up Client Notification</h2>
-<p>In addition to the programmatic function calls, to register interest for a server region and receive updated entries you need to configure the region with the <code>PROXY</code> or <code>CACHING_PROXY RegionShortcut</code> setting. The region’s pool should have <code>subscription-enabled=true</code> set either in the client XML or programmatically via a <code>CacheFactory::setSubscriptionEnabled(true)</code> API call. Otherwise, when you register interest, you will get an <code> [...]
+<p>In addition to the programmatic function calls, to register interest for a server region and receive updated entries you need to configure the region with the <code>PROXY</code> or <code>CACHING_PROXY RegionShortcut</code> setting. The region’s pool should have <code>subscription-enabled=true</code> set either in the client XML or programmatically via a <code>CacheFactory::SetSubscriptionEnabled(true)</code> API call. Otherwise, when you register interest, you will get an <code> [...]
<pre class="highlight plaintext"><code><region name="listenerWriterLoader" refid="CACHING_PROXY">
...
</code></pre>
@@ -283,48 +283,48 @@ limitations under the License.
<p><strong>Notification Sequence</strong></p>
-<p>Notifications invoke <code>CacheListeners</code> of cacheless clients in all cases for keys that have been registered on the server. Similarly, invalidates received from the server invoke <code>CacheListeners</code> of cacheless clients.</p>
+<p>Notifications invoke <code>CacheListeners</code> of cacheless clients in all cases for keys that have been registered on the server. Similarly, Invalidate events received from the server invoke <code>CacheListeners</code> of cacheless clients.</p>
-<p>If you register to receive notifications, listener callbacks are invoked irrespective of whether the key is in the client cache when a <code>destroy</code> or <code>invalidate</code> event is received.</p>
+<p>If you register to receive notifications, listener callbacks are invoked irrespective of whether the key is in the client cache when a <code>Destroy</code> or <code>Invalidate</code> event is received.</p>
<h2 id="registering-interest-for-specific-keys"><a id="registering-interest-for-entries__section_8772147940754C2D9688C789EB2F2AA6" class="no-quick-link"></a>Registering Interest for Specific Keys</h2>
-<p>You register and unregister interest for specific keys through the <code>registerKeys</code> and <code>unregisterKeys</code> functions. You register interest in a key or set of keys by specifying the key name using the programmatic syntax shown in the following example:</p>
+<p>You register and unregister interest for specific keys through the <code>RegisterKeys</code> and <code>UnregisterKeys</code> functions. You register interest in a key or set of keys by specifying the key name using the programmatic syntax shown in the following example:</p>
<pre class="highlight plaintext"><code>keys0.push_back(keyPtr1);
keys1.push_back(keyPtr3);
-regPtr0->registerKeys(keys0);
-regPtr1->registerKeys(keys1);
+regPtr0->RegisterKeys(keys0);
+regPtr1->RegisterKeys(keys1);
</code></pre>
<p>The programmatic code snippet in the next example shows how to unregister interest in specific keys:</p>
-<pre class="highlight plaintext"><code>regPtr0->unregisterKeys(keys0);
-regPtr1->unregisterKeys(keys1);
+<pre class="highlight plaintext"><code>regPtr0->UnregisterKeys(keys0);
+regPtr1->UnregisterKeys(keys1);
</code></pre>
<h2 id="registering-interest-for-all-keys"><a id="registering-interest-for-entries__section_EA4525CCDC474DD495410E948EAF566C" class="no-quick-link"></a>Registering Interest for All Keys</h2>
<p>If the client registers interest in all keys, the server provides notifications for all updates to all keys in the region. The next example shows how to register interest in all keys:</p>
-<pre class="highlight plaintext"><code>regPtr0->registerAllKeys();
-regPtr1->registerAllKeys();
+<pre class="highlight plaintext"><code>regPtr0->RegisterAllKeys();
+regPtr1->RegisterAllKeys();
</code></pre>
<p>The following example shows a code sample for unregistering interest in all keys.</p>
-<pre class="highlight plaintext"><code>regPtr0->unregisterAllKeys();
-regPtr1->unregisterAllKeys();
+<pre class="highlight plaintext"><code>regPtr0->UnregisterAllKeys();
+regPtr1->UnregisterAllKeys();
</code></pre>
<h2 id="registering-interest-using-regular-expressions"><a id="registering-interest-for-entries__section_BD50B80FCE9F429C8F6A9FEA818D5A91" class="no-quick-link"></a>Registering Interest Using Regular Expressions</h2>
-<p>The <code>registerRegex</code> function registers interest in a regular expression pattern. The server automatically sends the client changes for entries whose keys match the specified pattern.</p>
+<p>The <code>RegisterRegex</code> function registers interest in a regular expression pattern. The server automatically sends the client changes for entries whose keys match the specified pattern.</p>
<p><em>Keys must be strings in order to register interest using regular expressions.</em></p>
<p>The following example shows interest registration for all keys whose first four characters are <code>Key-</code>, followed by any string of characters. The characters <code>.*</code> represent a wildcard that matches any string.</p>
-<pre class="highlight plaintext"><code>regPtr1->registerRegex("Key-.*");
+<pre class="highlight plaintext"><code>regPtr1->RegisterRegex("Key-.*");
</code></pre>
-<p>To unregister interest using regular expressions, you use the <code>unregisterRegex</code> function. The next example shows how to unregister interest in all keys whose first four characters are <code>Key-</code>, followed by any string (represented by the <code>.*</code> wildcard).</p>
-<pre class="highlight plaintext"><code>regPtr1->unregisterRegex("Key-.*");
+<p>To unregister interest using regular expressions, you use the <code>UnregisterRegex</code> function. The next example shows how to unregister interest in all keys whose first four characters are <code>Key-</code>, followed by any string (represented by the <code>.*</code> wildcard).</p>
+<pre class="highlight plaintext"><code>regPtr1->UnregisterRegex("Key-.*");
</code></pre>
<h2 id="register-interest-scenario"><a id="registering-interest-for-entries__section_2D71A423B185493489129AAC30DC6733" class="no-quick-link"></a>Register Interest Scenario</h2>
diff --git a/docs/geode-native/dotnet/113/remote-queries.html b/docs/geode-native/dotnet/113/remote-queries.html
index 0dd2525..8c0eed9 100644
--- a/docs/geode-native/dotnet/113/remote-queries.html
+++ b/docs/geode-native/dotnet/113/remote-queries.html
@@ -283,6 +283,9 @@ You can optimize your queries by defining indexes on the cache server.</p>
<p>Querying and indexing operate only on remote cache server contents.</p>
+<p><strong>Note:</strong> Because floating point numbers can not reliably be compared for equality, do not use
+floating point values as keys or key components when constructing a query.</p>
+
<h3 id="query-language:-oql"><a id="QueryLanguage"></a>Query language: OQL</h3>
<p>Geode provides a SQL-like querying language called OQL that allows you to access data stored in Geode regions.
@@ -327,7 +330,7 @@ managing the compilation and execution of queries, and for retrieving an existin
<ol>
<li> Create an instance of the <code>QueryService</code> class. If you are using the pool API (recommended), you should obtain the <code>QueryService</code> from the pool.</li>
<li> Create a <code>Query</code> instance that is compatible with the OQL specification.</li>
-<li> Use the <code>Query.execute()</code> method to submit the query string to the cache server. The server
+<li> Use the <code>Query.Execute()</code> method to submit the query string to the cache server. The server
remotely evaluates the query string and returns the results to the client.</li>
<li> Iterate through the returned objects.</li>
</ol>
diff --git a/docs/geode-native/dotnet/113/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html b/docs/geode-native/dotnet/113/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
index e2057d5..b017e7f 100644
--- a/docs/geode-native/dotnet/113/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
+++ b/docs/geode-native/dotnet/113/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
@@ -272,9 +272,9 @@ is a single line of code to set the <code>PdxSerializer</code> to the .NET clien
<p>(The autoserializer can be registered only in the application code. It cannot be configured declaratively in <code>cache.xml</code>.)</p>
<p>After an autoserializer has been registered, all user classes can automatically be stored without needing to implement any
-interfaces. For example, the following <code>put</code> command stores <code>value</code>, which is an instance of a user defined class, in
+interfaces. For example, the following <code>Put</code> command stores <code>value</code>, which is an instance of a user defined class, in
the region.</p>
-<pre class="highlight csharp"><code><span class="n">region</span><span class="p">.</span><span class="nf">put</span><span class="p">(</span><span class="n">key</span><span class="p">,</span> <span class="k">value</span><span class="p">);</span>
+<pre class="highlight csharp"><code><span class="n">region</span><span class="p">.</span><span class="nf">Put</span><span class="p">(</span><span class="n">key</span><span class="p">,</span> <span class="k">value</span><span class="p">);</span>
</code></pre>
<p>The .NET client’s <code>ReflectionBasedAutoSerializer</code> supports the full list of .NET primitives and other common
diff --git a/docs/geode-native/dotnet/113/serialization/dotnet-serialization/pdx-serializable-examples.html b/docs/geode-native/dotnet/113/serialization/dotnet-serialization/pdx-serializable-examples.html
index 049340a..f21f3e4 100644
--- a/docs/geode-native/dotnet/113/serialization/dotnet-serialization/pdx-serializable-examples.html
+++ b/docs/geode-native/dotnet/113/serialization/dotnet-serialization/pdx-serializable-examples.html
@@ -265,8 +265,8 @@ can register for serialization of domain objects using the .NET IPdxSerializable
<p>The examples are located in <code>examples\dotnet\pdxserializable</code>.</p>
-<p>The examples define the serializable class, <code>Orders</code>, including its serialization and deserialization methods and its factory method.
-Once these pieces are in place, execution is simple: the main routine of the example registers the serializable class then performs some put and get operations.</p>
+<p>The example defines the serializable class, <code>Orders</code>, including its serialization and deserialization methods and its factory method.
+Once these pieces are in place, execution is simple: the main routine of the example registers the serializable class then performs some Put and Get operations.</p>
<p><a id="pdxsbl_execution"></a></p>
diff --git a/docs/geode-native/dotnet/113/serialization/dotnet-serialization/serialize-using-ipdxserializable.html b/docs/geode-native/dotnet/113/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
index 03e1108..96713ce 100644
--- a/docs/geode-native/dotnet/113/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
+++ b/docs/geode-native/dotnet/113/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
@@ -279,7 +279,7 @@ specify are deserialized.</p>
<ol>
<li> Write your domain class’s standard .NET data fields using the <code>IPdxWriter</code> write methods. Geode automatically provides <code>IPdxWriter</code> to the <code>ToData</code> function for <code>IPdxSerializable</code> objects.</li>
-<li><p>Call the <code>ToData markIdentifyField</code> function for each field Geode should use to identify your object. This is used to compare objects for operations like <code>DISTINCT</code> queries. The <code>markIdentifyField</code> call must come after the associated field write methods.</p>
+<li><p>Call the <code>ToData MarkIdentifyField</code> function for each field Geode should use to identify your object. This is used to compare objects for operations like <code>DISTINCT</code> queries. The <code>MarkIdentifyField</code> call must come after the associated field write methods.</p>
<p>Example:</p>
<pre class="highlight plaintext"><code>// object fields
@@ -352,7 +352,7 @@ public void ToData(IPdxWriter writer)
m_arrayZeroSize = reader.ReadByteArray("arrayZeroSize");
}
</code></pre></li>
-<li><p>Optionally, program your domain object’s <code>equals</code> and <code>hashcode</code> methods.</p></li>
+<li><p>Optionally, program your domain object’s <code>Equals</code> and <code>Hashcode</code> methods.</p></li>
</ol>
diff --git a/docs/geode-native/dotnet/113/transactions.html b/docs/geode-native/dotnet/113/transactions.html
index 20723b8..3f76833 100644
--- a/docs/geode-native/dotnet/113/transactions.html
+++ b/docs/geode-native/dotnet/113/transactions.html
@@ -273,8 +273,8 @@ For complete information about how transactions are conducted on the Geode serve
<h2 id="native-client-transaction-apis"><a id="client-transaction-apis"></a>Native Client Transaction APIs</h2>
-<p>The API for distributed transactions has the familiar relational database methods, <code>begin</code>,
-<code>commit</code>, and <code>rollback</code>. There are also APIs available to suspend and resume transactions.</p>
+<p>The API for distributed transactions has the familiar relational database methods, <code>Begin</code>,
+<code>Commit</code>, and <code>Rollback</code>. There are also APIs available to suspend and resume transactions.</p>
<p>The .NET classes for executing transactions are:</p>
@@ -289,7 +289,7 @@ For complete information about how transactions are conducted on the Geode serve
a client performs a transaction, the transaction is delegated to a server that brokers the
transaction.</p>
-<p>Start each transaction with a <code>begin</code> operation, and end the transaction with a <code>commit</code> or a <code>rollback</code>.</p>
+<p>Start each transaction with a <code>Begin</code> operation, and end the transaction with a <code>Commit</code> or a <code>Rollback</code>.</p>
<p>To maintain cache consistency, the local client cache is not used during a transaction.
When the transaction completes or is suspended, local cache usage is reinstated.</p>
@@ -356,7 +356,7 @@ For the complete source, see the example source directory.</p>
<p>Within the transaction, the client populates data store with 10 values associated with Key1 - Key10.</p>
<pre class="highlight csharp"><code> <span class="k">foreach</span><span class="p">(</span><span class="kt">var</span> <span class="n">key</span> <span class="k">in</span> <span class="n">keys</span><span class="p">)</span>
<span class="p">{</span>
- <span class="kt">var</span> <span class="k">value</span> <span class="p">=</span> <span class="nf">getValueFromExternalSystem</span><span class="p">();</span>
+ <span class="kt">var</span> <span class="k">value</span> <span class="p">=</span> <span class="nf">GetValueFromExternalSystem</span><span class="p">();</span>
<span class="n">region</span><span class="p">.</span><span class="nf">Put</span><span class="p">(</span><span class="n">key</span><span class="p">,</span> <span class="k">value</span><span class="p">);</span>
<span class="p">}</span>
</code></pre>
diff --git a/docs/geode-native/dotnet/114/continuous-queries.html b/docs/geode-native/dotnet/114/continuous-queries.html
index 7710c96..545bd19 100644
--- a/docs/geode-native/dotnet/114/continuous-queries.html
+++ b/docs/geode-native/dotnet/114/continuous-queries.html
@@ -312,14 +312,14 @@ floating point values as keys or key components when constructing a query.</p>
<ol>
<li> The client creates the CQ. This sets up everything for running the query and provides the client with a <code>CqQuery</code> object, but does not execute the CQ. At this point, the query is in a <code>STOPPED</code>state, ready to be closed or run.</li>
-<li><p>The client initiates the CQ with an API call to one of the <code>CqQuery execute*</code> methods. This puts the query into a <code>RUNNING</code> state on the client and on the server. The server remotely evaluates the query string, and optionally returns the results to the client. <code>CqQuery execute*</code> methods include:</p>
+<li><p>The client initiates the CQ with an API call to one of the <code>CqQuery Execute*</code> methods. This puts the query into a <code>RUNNING</code> state on the client and on the server. The server remotely evaluates the query string, and optionally returns the results to the client. <code>CqQuery Execute*</code> methods include:</p>
<ul>
<li><code>CqQuery.Execute()</code></li>
<li><code>CqQuery.ExecuteWithInitialResults()</code></li>
</ul></li>
<li><p>A CQ Listener waits for events. When it receives events, it takes action accordingly with the data in the CqEvent.</p></li>
-<li><p>The CQ is closed by a client call to <code>CqQuery.close</code>. This de-allocates all resources in use for the CQ on the client and server. At this point, the cycle could begin again with the creation of a new <code>CqQuery</code> instance.</p></li>
+<li><p>The CQ is closed by a client call to <code>CqQuery.Close</code>. This de-allocates all resources in use for the CQ on the client and server. At this point, the cycle could begin again with the creation of a new <code>CqQuery</code> instance.</p></li>
</ol>
<h2 id="executing-a-continuous-query-from-the-client"><a id="ExecutingACQ"></a>Executing a Continuous Query from the Client</h2>
@@ -329,7 +329,7 @@ floating point values as keys or key components when constructing a query.</p>
<ol>
<li> Create an instance of the <code>QueryService</code> class. If you are using the pool API (recommended), you should obtain the <code>QueryService</code> from the pool.</li>
<li> Define a CQ Listener (an <code>ICqListener</code>) to field events sent from the server.</li>
-<li> Use one of the <code>CqQuery execute*</code> methods to submit the query string to the cache server.</li>
+<li> Use one of the <code>CqQuery Execute*</code> methods to submit the query string to the cache server.</li>
<li> The server remotely evaluates the query string, then monitors those results and notifies the client if they change.</li>
<li> The client listens for changes that match the query predicate.</li>
<li> Iterate through the returned objects.</li>
diff --git a/docs/geode-native/dotnet/114/function-execution.html b/docs/geode-native/dotnet/114/function-execution.html
index 96f597e..1ae38c6 100644
--- a/docs/geode-native/dotnet/114/function-execution.html
+++ b/docs/geode-native/dotnet/114/function-execution.html
@@ -304,36 +304,36 @@ in the Geode User Guide for details on how to write and register server-resident
<h2 id="how-functions-execute"><a id="nc-fe-how_functions_execute"></a>How Functions Execute</h2>
<ol>
-<li> The calling client application runs the <code>execute</code> method on the <code>Execution</code> object. The function must already be registered on the servers.</li>
-<li> The function is invoked on the servers where it needs to run. The servers are determined by the <code>FunctionService on*</code>
+<li> The calling client application runs the <code>Execute</code> method on the <code>Execution</code> object. The function must already be registered on the servers.</li>
+<li> The function is invoked on the servers where it needs to run. The servers are determined by the <code>FunctionService On*</code>
method calls, region configuration, and any filters.</li>
<li> If the function has results, the result is returned in a <code>ResultCollector</code> object.</li>
-<li> The client collects results using the <code>ResultCollector.getResult()</code> method.</li>
+<li> The client collects results using the <code>ResultCollector.GetResult()</code> method.</li>
</ol>
<p>In every client where you want to execute the function and process the results:</p>
<ul>
-<li>Use one of the <code>FunctionService on*</code> methods to create an <code>Execution</code> object. The <code>on*</code> methods,
-<code>onRegion</code>, <code>onServer</code> and <code>onServers</code>, define the highest level where the function is run.</li>
-<li>If you use <code>onRegion</code> you can further narrow your run scope by setting key filters.</li>
-<li>A function run using <code>onRegion</code> is a <em>data dependent</em> function – others are <em>data-independent</em> functions.</li>
+<li>Use one of the <code>FunctionService On*</code> methods to create an <code>Execution</code> object. The <code>On*</code> methods,
+<code>OnRegion</code>, <code>OnServer</code> and <code>OnServers</code>, define the highest level where the function is run.</li>
+<li>If you use <code>OnRegion</code> you can further narrow your run scope by setting key filters.</li>
+<li>A function run using <code>OnRegion</code> is a <em>data dependent</em> function – others are <em>data-independent</em> functions.</li>
<li><p>You can run a data dependent function against partitioned and colocated partitioned regions. From the client, provide the appropriate key
sets to the function call.</p></li>
<li><p>The <code>Execution</code> object allows you to customize the invocation by:</p>
<ul>
-<li> Providing a set of data keys to <code>withFilter</code> to narrow the execution scope. This works only for <code>onRegion</code> Execution objects (data-dependent functions).</li>
-<li> Providing function arguments to <code>withArgs</code>.</li>
-<li> Defining a custom <code>ResultCollector</code> for <code>withCollector</code>.</li>
+<li> Providing a set of data keys to <code>WithFilter</code> to narrow the execution scope. This works only for <code>OnRegion</code> Execution objects (data-dependent functions).</li>
+<li> Providing function arguments to <code>WithArgs</code>.</li>
+<li> Defining a custom <code>ResultCollector</code> for <code>WithCollector</code>.</li>
</ul></li>
-<li><p>Call the <code>Execution.execute()</code> method to run the function.</p></li>
+<li><p>Call the <code>Execution.Execute()</code> method to run the function.</p></li>
</ul>
<h2 id="processing-function-results"><a id="nc-fe-processing_function_results"></a>Processing Function Results</h2>
<p>To get the results from the function in the client app, use the result collector returned from the function execution.
-The <code>getResult</code> methods of the default result collector block until all results are received, then return the full result set.</p>
+The <code>GetResult</code> methods of the default result collector block until all results are received, then return the full result set.</p>
<p>The client can use the default result collector. If the client needs special results handling, code a custom <code>ResultsCollector</code> implementation to replace the default.
Use the <code>Execution::withCollector</code> method to specify the custom collector.
@@ -343,12 +343,12 @@ To handle the results in a custom manner:</p>
<li> Write a class that implements the <code>ResultCollector</code> interface to handle the results in a custom manner. The methods are of two types: one handles data and information from Geode and populates the results set, while the other returns the compiled results to the calling application:
<ul>
-<li> <code>addResult</code> is called when results arrive from the <code>Function</code> methods. Use <code>addResult</code> to add a single result to the ResultCollector.</li>
-<li> <code>endResults</code> is called to signal the end of all results from the function execution.</li>
-<li> <code>getResult</code> is available to your executing application (the one that calls <code>Execution.execute</code>) to retrieve the results. This may block until all results are available.</li>
-<li> <code>clearResults</code> is called to clear partial results from the results collector. This is used only for highly available <code>onRegion</code> functions where the calling application waits for the results. If the call fails, before Geode retries the execution, it calls <code>clearResults</code> to ready the instance for a clean set of results.</li>
+<li> <code>AddResult</code> is called when results arrive from the <code>Function</code> methods. Use <code>AddResult</code> to add a single result to the ResultCollector.</li>
+<li> <code>EndResults</code> is called to signal the end of all results from the function execution.</li>
+<li> <code>GetResult</code> is available to your executing application (the one that calls <code>Execution.Execute</code>) to retrieve the results. This may block until all results are available.</li>
+<li> <code>ClearResults</code> is called to clear partial results from the results collector. This is used only for highly available <code>OnRegion</code> functions where the calling application waits for the results. If the call fails, before Geode retries the execution, it calls <code>ClearResults</code> to ready the instance for a clean set of results.</li>
</ul></li>
-<li> Use the <code>Execution</code> object in your executing member to call <code>withCollector</code>, passing your custom collector.</li>
+<li> Use the <code>Execution</code> object in your executing member to call <code>WithCollector</code>, passing your custom collector.</li>
</ol>
<h2 id="function-execution-example"><a id="nc-fe-examples"></a>Function Execution Example</h2>
@@ -360,7 +360,7 @@ To handle the results in a custom manner:</p>
<li>The function is preloaded with a JAR file containing the server-side Java function code. </li>
<li>The function, called “ExampleMultiGetFunction”, is defined in the
<code>examples/utilities</code> directory of your distribution. As its input parameter, the function takes an array of keys,
-then performs a <code>get</code> on each key and returns an array containing the results.</li>
+then performs a <code>Get</code> on each key and returns an array containing the results.</li>
<li>The function does not load values into the data store. That is a separate operation, performed in these examples by
the client, and does not involve the server-side function.</li>
</ul>
@@ -377,7 +377,7 @@ of the input parameter and return value.</p>
</ul>
<p>If the client expects results, it must create a result object.
-The .NET example uses a built-in result collector (<code>IResultCollector.getResults()</code>) to retrieve the function results.</p>
+The .NET example uses a built-in result collector (<code>IResultCollector.GetResults()</code>) to retrieve the function results.</p>
<h3 id=".net-example"><a id="nc-fe-dotnet_example"></a>.NET Example</h3>
diff --git a/docs/geode-native/dotnet/114/preserving-data/config-durable-interest-keys.html b/docs/geode-native/dotnet/114/preserving-data/config-durable-interest-keys.html
index 3d5f951..aca9e9a 100644
--- a/docs/geode-native/dotnet/114/preserving-data/config-durable-interest-keys.html
+++ b/docs/geode-native/dotnet/114/preserving-data/config-durable-interest-keys.html
@@ -9,7 +9,6 @@
<link href='https://fonts.googleapis.com/css?family=Source+Sans+Pro:300,300italic,400italic,400,600' rel='stylesheet' type='text/css'>
<!-- Use title if it's in the page YAML frontmatter -->
<title>
- Configuring Durable Interest in Keys |
Geode Native .NET Docs
</title>
<meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -248,9 +247,6 @@ 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.
-->
- <h1 class="title-container" >
- Configuring Durable Interest in Keys
- </h1>
<div id="js-quick-links" >
@@ -258,7 +254,11 @@ limitations under the License.
<div class="to-top" id="js-to-top">
<a href="#top" title="back to top"></a>
</div>
- <!--
+ <p>–</p>
+
+<h2 id="title:-configuring-durable-interest-in-keys">title: Configuring Durable Interest in Keys</h2>
+
+<!--
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.
@@ -281,7 +281,7 @@ limitations under the License.
<p>You still register interest for other keys, but not durable interest. When the client is connected to its servers, it receives messages for those non-durable keys. When the client is disconnected, its non-durable interest registrations are deleted but messages that are already in the queue remain there.</p>
-<p>For durable clients, all interest registration is done immediately after the regions are created. This is required whether interest registration is durable or not durable. An extra <code>registerInterest</code> parameter specified for durable clients indicates whether the registration is durable (true) or not (false).</p>
+<p>For durable clients, all interest registration is done immediately after the regions are created. This is required whether interest registration is durable or not durable. An extra <code>RegisterInterest</code> parameter specified for durable clients indicates whether the registration is durable (true) or not (false).</p>
<h2 id="api-client-durable-interest-list-registration-(c++)">API Client Durable Interest List Registration (C++)</h2>
@@ -290,7 +290,7 @@ limitations under the License.
// durable (true) or nondurable(default).
VectorOfCacheableKey keys;
keys.push_back( CacheableString::create("Key-1") );
-regionPtr->registerKeys(keys,true);
+regionPtr->RegisterKeys(keys,true);
</code></pre>
<p><a id="concept_6456354A9AD945C780A5AA864B41B564__section_3DE5872B0888410EB42D52CFB28C79E5"></a>
diff --git a/docs/geode-native/dotnet/114/regions/registering-interest-for-entries.html b/docs/geode-native/dotnet/114/regions/registering-interest-for-entries.html
index a9cd984..02e4b9e 100644
--- a/docs/geode-native/dotnet/114/regions/registering-interest-for-entries.html
+++ b/docs/geode-native/dotnet/114/regions/registering-interest-for-entries.html
@@ -279,17 +279,17 @@ limitations under the License.
<p>You can register interest for specific entry keys or for all keys. Regular expressions can be used to register interest for keys whose strings match the expression. You can also unregister interest for specific keys, groups of keys based on regular expressions, or for all keys.</p>
-<p><strong>Note:</strong> Interest registration and unregistration are symmetrical operations. Consequently, you cannot register interest in all keys and then unregister interest in a specific set of keys. Also, if you first register interest in specific keys with <code>registerKeys</code>, then call <code>registerAllKeys</code>, you must call <code>unregisterAllKeys</code> before specifying interest in specific keys again.</p>
+<p><strong>Note:</strong> Interest registration and unregistration are symmetrical operations. Consequently, you cannot register interest in all keys and then unregister interest in a specific set of keys. Also, if you first register interest in specific keys with <code>RegisterKeys</code>, then call <code>RegisterAllKeys</code>, you must call <code>UnregisterAllKeys</code> before specifying interest in specific keys again.</p>
<h2 id="client-api-for-registering-interest"><a id="registering-interest-for-entries__section_C9A3D7F193B24ACD83B2D67813E596A0" class="no-quick-link"></a>Client API for Registering Interest</h2>
<p>You register client interest through the .NET API. The .NET API provides the <code>RegisterKeys</code>, <code>RegisterAllKeys</code>, and <code>RegisterRegex</code> methods, with corresponding unregistration accomplished using the <code>UnregisterKeys</code>, <code>UnregisterAllKeys</code>, and <code>UnregisterRegex</code> methods.</p>
-<p>The <code>registerKeys</code>, <code>registerRegex</code> and <code>registerAllKeys</code> methods have the option to populate the cache with the registration results from the server. The <code>registerRegex</code> and <code>registerAllKeys</code> methods can also optionally return the current list of keys registered on the server.</p>
+<p>The <code>RegisterKeys</code>, <code>RegisterRegex</code> and <code>RegisterAllKeys</code> methods have the option to populate the cache with the registration results from the server. The <code>RegisterRegex</code> and <code>RegisterAllKeys</code> methods can also optionally return the current list of keys registered on the server.</p>
<h2 id="setting-up-client-notification"><a id="registering-interest-for-entries__section_C1A3F89EE73448D7AFF2076F41848F55" class="no-quick-link"></a>Setting Up Client Notification</h2>
-<p>In addition to the programmatic function calls, to register interest for a server region and receive updated entries you need to configure the region with the <code>PROXY</code> or <code>CACHING_PROXY RegionShortcut</code> setting. The region’s pool should have <code>subscription-enabled=true</code> set either in the client XML or programmatically via a <code>CacheFactory::setSubscriptionEnabled(true)</code> API call. Otherwise, when you register interest, you will get an <code> [...]
+<p>In addition to the programmatic function calls, to register interest for a server region and receive updated entries you need to configure the region with the <code>PROXY</code> or <code>CACHING_PROXY RegionShortcut</code> setting. The region’s pool should have <code>subscription-enabled=true</code> set either in the client XML or programmatically via a <code>CacheFactory::SetSubscriptionEnabled(true)</code> API call. Otherwise, when you register interest, you will get an <code> [...]
<pre class="highlight plaintext"><code><region name="listenerWriterLoader" refid="CACHING_PROXY">
...
</code></pre>
@@ -298,48 +298,48 @@ limitations under the License.
<p><strong>Notification Sequence</strong></p>
-<p>Notifications invoke <code>CacheListeners</code> of cacheless clients in all cases for keys that have been registered on the server. Similarly, invalidates received from the server invoke <code>CacheListeners</code> of cacheless clients.</p>
+<p>Notifications invoke <code>CacheListeners</code> of cacheless clients in all cases for keys that have been registered on the server. Similarly, Invalidate events received from the server invoke <code>CacheListeners</code> of cacheless clients.</p>
-<p>If you register to receive notifications, listener callbacks are invoked irrespective of whether the key is in the client cache when a <code>destroy</code> or <code>invalidate</code> event is received.</p>
+<p>If you register to receive notifications, listener callbacks are invoked irrespective of whether the key is in the client cache when a <code>Destroy</code> or <code>Invalidate</code> event is received.</p>
<h2 id="registering-interest-for-specific-keys"><a id="registering-interest-for-entries__section_8772147940754C2D9688C789EB2F2AA6" class="no-quick-link"></a>Registering Interest for Specific Keys</h2>
-<p>You register and unregister interest for specific keys through the <code>registerKeys</code> and <code>unregisterKeys</code> functions. You register interest in a key or set of keys by specifying the key name using the programmatic syntax shown in the following example:</p>
+<p>You register and unregister interest for specific keys through the <code>RegisterKeys</code> and <code>UnregisterKeys</code> functions. You register interest in a key or set of keys by specifying the key name using the programmatic syntax shown in the following example:</p>
<pre class="highlight plaintext"><code>keys0.push_back(keyPtr1);
keys1.push_back(keyPtr3);
-regPtr0->registerKeys(keys0);
-regPtr1->registerKeys(keys1);
+regPtr0->RegisterKeys(keys0);
+regPtr1->RegisterKeys(keys1);
</code></pre>
<p>The programmatic code snippet in the next example shows how to unregister interest in specific keys:</p>
-<pre class="highlight plaintext"><code>regPtr0->unregisterKeys(keys0);
-regPtr1->unregisterKeys(keys1);
+<pre class="highlight plaintext"><code>regPtr0->UnregisterKeys(keys0);
+regPtr1->UnregisterKeys(keys1);
</code></pre>
<h2 id="registering-interest-for-all-keys"><a id="registering-interest-for-entries__section_EA4525CCDC474DD495410E948EAF566C" class="no-quick-link"></a>Registering Interest for All Keys</h2>
<p>If the client registers interest in all keys, the server provides notifications for all updates to all keys in the region. The next example shows how to register interest in all keys:</p>
-<pre class="highlight plaintext"><code>regPtr0->registerAllKeys();
-regPtr1->registerAllKeys();
+<pre class="highlight plaintext"><code>regPtr0->RegisterAllKeys();
+regPtr1->RegisterAllKeys();
</code></pre>
<p>The following example shows a code sample for unregistering interest in all keys.</p>
-<pre class="highlight plaintext"><code>regPtr0->unregisterAllKeys();
-regPtr1->unregisterAllKeys();
+<pre class="highlight plaintext"><code>regPtr0->UnregisterAllKeys();
+regPtr1->UnregisterAllKeys();
</code></pre>
<h2 id="registering-interest-using-regular-expressions"><a id="registering-interest-for-entries__section_BD50B80FCE9F429C8F6A9FEA818D5A91" class="no-quick-link"></a>Registering Interest Using Regular Expressions</h2>
-<p>The <code>registerRegex</code> function registers interest in a regular expression pattern. The server automatically sends the client changes for entries whose keys match the specified pattern.</p>
+<p>The <code>RegisterRegex</code> function registers interest in a regular expression pattern. The server automatically sends the client changes for entries whose keys match the specified pattern.</p>
<p><em>Keys must be strings in order to register interest using regular expressions.</em></p>
<p>The following example shows interest registration for all keys whose first four characters are <code>Key-</code>, followed by any string of characters. The characters <code>.*</code> represent a wildcard that matches any string.</p>
-<pre class="highlight plaintext"><code>regPtr1->registerRegex("Key-.*");
+<pre class="highlight plaintext"><code>regPtr1->RegisterRegex("Key-.*");
</code></pre>
-<p>To unregister interest using regular expressions, you use the <code>unregisterRegex</code> function. The next example shows how to unregister interest in all keys whose first four characters are <code>Key-</code>, followed by any string (represented by the <code>.*</code> wildcard).</p>
-<pre class="highlight plaintext"><code>regPtr1->unregisterRegex("Key-.*");
+<p>To unregister interest using regular expressions, you use the <code>UnregisterRegex</code> function. The next example shows how to unregister interest in all keys whose first four characters are <code>Key-</code>, followed by any string (represented by the <code>.*</code> wildcard).</p>
+<pre class="highlight plaintext"><code>regPtr1->UnregisterRegex("Key-.*");
</code></pre>
<h2 id="register-interest-scenario"><a id="registering-interest-for-entries__section_2D71A423B185493489129AAC30DC6733" class="no-quick-link"></a>Register Interest Scenario</h2>
diff --git a/docs/geode-native/dotnet/114/remote-queries.html b/docs/geode-native/dotnet/114/remote-queries.html
index d0c7b3a..80080b3 100644
--- a/docs/geode-native/dotnet/114/remote-queries.html
+++ b/docs/geode-native/dotnet/114/remote-queries.html
@@ -345,7 +345,7 @@ managing the compilation and execution of queries, and for retrieving an existin
<ol>
<li> Create an instance of the <code>QueryService</code> class. If you are using the pool API (recommended), you should obtain the <code>QueryService</code> from the pool.</li>
<li> Create a <code>Query</code> instance that is compatible with the OQL specification.</li>
-<li> Use the <code>Query.execute()</code> method to submit the query string to the cache server. The server
+<li> Use the <code>Query.Execute()</code> method to submit the query string to the cache server. The server
remotely evaluates the query string and returns the results to the client.</li>
<li> Iterate through the returned objects.</li>
</ol>
diff --git a/docs/geode-native/dotnet/114/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html b/docs/geode-native/dotnet/114/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
index 8be601b..bfe832a 100644
--- a/docs/geode-native/dotnet/114/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
+++ b/docs/geode-native/dotnet/114/serialization/dotnet-serialization/dotnet-pdx-autoserializer.html
@@ -287,9 +287,9 @@ is a single line of code to set the <code>PdxSerializer</code> to the .NET clien
<p>(The autoserializer can be registered only in the application code. It cannot be configured declaratively in <code>cache.xml</code>.)</p>
<p>After an autoserializer has been registered, all user classes can automatically be stored without needing to implement any
-interfaces. For example, the following <code>put</code> command stores <code>value</code>, which is an instance of a user defined class, in
+interfaces. For example, the following <code>Put</code> command stores <code>value</code>, which is an instance of a user defined class, in
the region.</p>
-<pre class="highlight csharp"><code><span class="n">region</span><span class="p">.</span><span class="nf">put</span><span class="p">(</span><span class="n">key</span><span class="p">,</span> <span class="k">value</span><span class="p">);</span>
+<pre class="highlight csharp"><code><span class="n">region</span><span class="p">.</span><span class="nf">Put</span><span class="p">(</span><span class="n">key</span><span class="p">,</span> <span class="k">value</span><span class="p">);</span>
</code></pre>
<p>The .NET client’s <code>ReflectionBasedAutoSerializer</code> supports the full list of .NET primitives and other common
diff --git a/docs/geode-native/dotnet/114/serialization/dotnet-serialization/pdx-serializable-examples.html b/docs/geode-native/dotnet/114/serialization/dotnet-serialization/pdx-serializable-examples.html
index 1db068d..9426675 100644
--- a/docs/geode-native/dotnet/114/serialization/dotnet-serialization/pdx-serializable-examples.html
+++ b/docs/geode-native/dotnet/114/serialization/dotnet-serialization/pdx-serializable-examples.html
@@ -281,7 +281,7 @@ can register for serialization of domain objects using the .NET IPdxSerializable
<p>The example is located in <code>examples\dotnet\pdxserializable</code>.</p>
<p>The example defines the serializable class, <code>Orders</code>, including its serialization and deserialization methods and its factory method.
-Once these pieces are in place, execution is simple: the main routine of the example registers the serializable class then performs some put and get operations.</p>
+Once these pieces are in place, execution is simple: the main routine of the example registers the serializable class then performs some Put and Get operations.</p>
<p><a id="pdxsbl_execution"></a></p>
diff --git a/docs/geode-native/dotnet/114/serialization/dotnet-serialization/serialize-using-ipdxserializable.html b/docs/geode-native/dotnet/114/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
index 4549130..7ebef7c 100644
--- a/docs/geode-native/dotnet/114/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
+++ b/docs/geode-native/dotnet/114/serialization/dotnet-serialization/serialize-using-ipdxserializable.html
@@ -294,7 +294,7 @@ specify are deserialized.</p>
<ol>
<li> Write your domain class’s standard .NET data fields using the <code>IPdxWriter</code> write methods. Geode automatically provides <code>IPdxWriter</code> to the <code>ToData</code> function for <code>IPdxSerializable</code> objects.</li>
-<li><p>Call the <code>ToData markIdentifyField</code> function for each field Geode should use to identify your object. This is used to compare objects for operations like <code>DISTINCT</code> queries. The <code>markIdentifyField</code> call must come after the associated field write methods.</p>
+<li><p>Call the <code>ToData MarkIdentifyField</code> function for each field Geode should use to identify your object. This is used to compare objects for operations like <code>DISTINCT</code> queries. The <code>MarkIdentifyField</code> call must come after the associated field write methods.</p>
<p>Example:</p>
<pre class="highlight plaintext"><code>// object fields
@@ -367,7 +367,7 @@ public void ToData(IPdxWriter writer)
m_arrayZeroSize = reader.ReadByteArray("arrayZeroSize");
}
</code></pre></li>
-<li><p>Optionally, program your domain object’s <code>equals</code> and <code>hashcode</code> methods.</p></li>
+<li><p>Optionally, program your domain object’s <code>Equals</code> and <code>Hashcode</code> methods.</p></li>
</ol>
diff --git a/docs/geode-native/dotnet/114/transactions.html b/docs/geode-native/dotnet/114/transactions.html
index d1e47f8..43530cb 100644
--- a/docs/geode-native/dotnet/114/transactions.html
+++ b/docs/geode-native/dotnet/114/transactions.html
@@ -288,8 +288,8 @@ For complete information about how transactions are conducted on the Geode serve
<h2 id="native-client-transaction-apis"><a id="client-transaction-apis"></a>Native Client Transaction APIs</h2>
-<p>The API for distributed transactions has the familiar relational database methods, <code>begin</code>,
-<code>commit</code>, and <code>rollback</code>. There are also APIs available to suspend and resume transactions.</p>
+<p>The API for distributed transactions has the familiar relational database methods, <code>Begin</code>,
+<code>Commit</code>, and <code>Rollback</code>. There are also APIs available to suspend and resume transactions.</p>
<p>The .NET classes for executing transactions are:</p>
@@ -304,7 +304,7 @@ For complete information about how transactions are conducted on the Geode serve
a client performs a transaction, the transaction is delegated to a server that brokers the
transaction.</p>
-<p>Start each transaction with a <code>begin</code> operation, and end the transaction with a <code>commit</code> or a <code>rollback</code>.</p>
+<p>Start each transaction with a <code>Begin</code> operation, and end the transaction with a <code>Commit</code> or a <code>Rollback</code>.</p>
<p>To maintain cache consistency, the local client cache is not used during a transaction.
When the transaction completes or is suspended, local cache usage is reinstated.</p>
@@ -372,7 +372,7 @@ For the complete source, see the example source directory.</p>
<p>Within the transaction, the client populates data store with 10 values associated with Key1 - Key10.</p>
<pre class="highlight csharp"><code> <span class="k">foreach</span><span class="p">(</span><span class="kt">var</span> <span class="n">key</span> <span class="k">in</span> <span class="n">keys</span><span class="p">)</span>
<span class="p">{</span>
- <span class="kt">var</span> <span class="k">value</span> <span class="p">=</span> <span class="nf">getValueFromExternalSystem</span><span class="p">();</span>
+ <span class="kt">var</span> <span class="k">value</span> <span class="p">=</span> <span class="nf">GetValueFromExternalSystem</span><span class="p">();</span>
<span class="n">region</span><span class="p">.</span><span class="nf">Put</span><span class="p">(</span><span class="n">key</span><span class="p">,</span> <span class="k">value</span><span class="p">);</span>
<span class="p">}</span>
</code></pre>