This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode-native.git
The following commit(s) were added to refs/heads/develop by this push:
new 1f0bd2d GEODE-4728: User Guide -Modify data serialization navigation
1f0bd2d is described below
commit 1f0bd2dd75762f2fa91f2857f59e9623a2557d56
Author: Dave Barnes <[email protected]>
AuthorDate: Tue Jul 24 09:43:17 2018 -0700
GEODE-4728: User Guide -Modify data serialization navigation
---
.../about-client-users-guide.html.md.erb | 2 +-
.../configuring/configuration.html.md.erb | 3 ++-
.../cpp-serialization/serialization-options.html.md.erb | 15 +++------------
.../cpp-serialization/serialization-overview.html.md.erb | 2 +-
.../serialization/data-serialization.html.md.erb | 5 +----
5 files changed, 8 insertions(+), 19 deletions(-)
diff --git a/docs/geode-native-docs/about-client-users-guide.html.md.erb
b/docs/geode-native-docs/about-client-users-guide.html.md.erb
index 89db895..a43e22c 100644
--- a/docs/geode-native-docs/about-client-users-guide.html.md.erb
+++ b/docs/geode-native-docs/about-client-users-guide.html.md.erb
@@ -17,7 +17,7 @@ See the License for the specific language governing
permissions and
limitations under the License.
-->
-Published July 17, 2018
+Published July 23, 2018
This documentation describes the <%=vars.product_name_long%> Native Client.
diff --git a/docs/geode-native-docs/configuring/configuration.html.md.erb
b/docs/geode-native-docs/configuring/configuration.html.md.erb
index d6a4294..76ed266 100644
--- a/docs/geode-native-docs/configuring/configuration.html.md.erb
+++ b/docs/geode-native-docs/configuring/configuration.html.md.erb
@@ -92,6 +92,7 @@ programmatically or in the `geode.properties` file.
When redundancy is enabled, secondary servers maintain queue backups while the
primary server pushes
events to the client. If the primary server fails, one of the secondary
servers steps in as primary
to provide uninterrupted event messaging to the client.
+To configure high availability, set the `subscription-redundancy` in the
client’s pool configuration. This setting indicates the number of secondary
servers to use.
See the _<%=vars.product_name%> User Guide_ section [Configuring Highly
Available
Servers](/serverman/developing/events/configuring_highly_available_servers.html)
-for details on configuring your system for high availability with server
redundancy.
+for more details.
diff --git
a/docs/geode-native-docs/serialization/cpp-serialization/serialization-options.html.md.erb
b/docs/geode-native-docs/serialization/cpp-serialization/serialization-options.html.md.erb
index b0cc016..780210c 100644
---
a/docs/geode-native-docs/serialization/cpp-serialization/serialization-options.html.md.erb
+++
b/docs/geode-native-docs/serialization/cpp-serialization/serialization-options.html.md.erb
@@ -37,12 +37,7 @@ When using PDX serialization, you can use either
`PdxSerializable` (for a specif
The non-PDX serialization option is to use the
`apache::geode::client::DataSerializable` interface. This
`DataSerializable` interface can be a good option performance-wise if the size
of your objects is
small. `DataSerializable` is used whenever a user domain class is not
inherited by `PdxSerializable`,
-but the user has registered the class with the `registerType` API. See
[Serializing Data with the
-DataSerializable
-Interface](serialization-using-serializable.html#concept_696AB5206C3E45898CC1A24CDD93D003)
for more
-information.
-
-<a
id="concept_7B6F272ACEA14753A723CB73B858ADBE__table_D61A94C4BFBE4712835F632F30BB488E"></a>
+but the user has registered the class with the `registerType` API.
<table>
<caption><span class="tablecap">Table 1. Serialization Options—Comparison of
Features</span></caption>
@@ -60,7 +55,7 @@ information.
</thead>
<tbody>
<tr class="odd">
-<td><p>Handles multiple versions of domain objects*</p></td>
+<td><p>Handles multiple versions of domain objects</p></td>
<td></td>
<td>X</td>
</tr>
@@ -77,14 +72,10 @@ information.
<tr class="even">
<td><p>Works with Geode delta propagation</p></td>
<td>X</td>
-<td>X**</td>
+<td>X</td>
</tr>
</tbody>
</table>
<span class="tablecap">**Table 1.** Serialization Options—Comparison of
Features</span>
-\* You can mix domain object versions where the differences between versions
are the addition and removal of object fields.
-
-\*\* See [Using PDX Serialization with Delta
Propagation](pdx-with-delta-propagation.html#concept_F33AC930A8F14F0A9EE07AC31FFD8C8F)
for requirements.
-
diff --git
a/docs/geode-native-docs/serialization/cpp-serialization/serialization-overview.html.md.erb
b/docs/geode-native-docs/serialization/cpp-serialization/serialization-overview.html.md.erb
index 86fa1fe..6c5ba24 100644
---
a/docs/geode-native-docs/serialization/cpp-serialization/serialization-overview.html.md.erb
+++
b/docs/geode-native-docs/serialization/cpp-serialization/serialization-overview.html.md.erb
@@ -23,7 +23,7 @@ All data moving out of the client cache must be serializable.
- **[Data Serialization Options](serialization-options.html)**
- The C++ client API provides two serialization options: the
`apache::geode::client::Serializable` interface and <%=vars.product_name%> PDX
serialization.
+ The C++ client API provides two serialization options:
<%=vars.product_name%> PDX serialization and the
`apache::geode::client::DataSerializable` interface.
- **[Using PDX Serialization](pdx-serialization.html)**
diff --git
a/docs/geode-native-docs/serialization/data-serialization.html.md.erb
b/docs/geode-native-docs/serialization/data-serialization.html.md.erb
index 265d215..10366b9 100644
--- a/docs/geode-native-docs/serialization/data-serialization.html.md.erb
+++ b/docs/geode-native-docs/serialization/data-serialization.html.md.erb
@@ -25,8 +25,5 @@ Data in your client application's <%=vars.product_name%>
cache must be serializa
between processes, of which **<%=vars.product_name%> Portable Data eXchange
(PDX) serialization** offers
the best combination of versatility and ease-of-use for most applications.
-To learn more about other serialization options, see the subtopics in this
section describing serialization for the C++ and .NET APIs,
-[Data Serialization - C++](cpp-serialization/serialization-overview.html) and
-[Data Serialization -
.NET](dotnet-serialization/dotnet-data-serialization.html),
-and the [Data Serialization section in the _<%=vars.product_name_long%> User
Guide_](/serverman/developing/data_serialization/chapter_overview.html).
+To learn more about other serialization options, see the [Data Serialization
section in the _<%=vars.product_name_long%> User
Guide_](/serverman/developing/data_serialization/chapter_overview.html).
