Consolidated two sources, eliminating GemFire versions in favor of a single Geode version: Using gfsh to manage a remote cluster and Overview of data serialization. [#126263243]
Project: http://git-wip-us.apache.org/repos/asf/incubator-geode/repo Commit: http://git-wip-us.apache.org/repos/asf/incubator-geode/commit/2bd8128e Tree: http://git-wip-us.apache.org/repos/asf/incubator-geode/tree/2bd8128e Diff: http://git-wip-us.apache.org/repos/asf/incubator-geode/diff/2bd8128e Branch: refs/heads/staging/docs-grant1 Commit: 2bd8128ee17d7c76b72e0a4d3f4ae1ce29547034 Parents: e2d0ced Author: Dave Barnes <[email protected]> Authored: Tue Sep 20 15:45:59 2016 -0700 Committer: Dave Barnes <[email protected]> Committed: Tue Sep 20 15:45:59 2016 -0700 ---------------------------------------------------------------------- configuring/cluster_config/gfsh_remote.html.md.erb | 1 + .../data_serialization/data_serialization_options.html.md.erb | 4 ++++ 2 files changed, 5 insertions(+) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/2bd8128e/configuring/cluster_config/gfsh_remote.html.md.erb ---------------------------------------------------------------------- diff --git a/configuring/cluster_config/gfsh_remote.html.md.erb b/configuring/cluster_config/gfsh_remote.html.md.erb index 4dc0039..9132e44 100644 --- a/configuring/cluster_config/gfsh_remote.html.md.erb +++ b/configuring/cluster_config/gfsh_remote.html.md.erb @@ -39,6 +39,7 @@ To connect `gfsh` using the HTTP protocol to a remote GemFire cluster: - `start jvisualvm` - `start locator` - `start server` + - `start vsd` - `status locator``*` - `status server``*` - `stop locator``*` http://git-wip-us.apache.org/repos/asf/incubator-geode/blob/2bd8128e/developing/data_serialization/data_serialization_options.html.md.erb ---------------------------------------------------------------------- diff --git a/developing/data_serialization/data_serialization_options.html.md.erb b/developing/data_serialization/data_serialization_options.html.md.erb index fce15d6..7402ee7 100644 --- a/developing/data_serialization/data_serialization_options.html.md.erb +++ b/developing/data_serialization/data_serialization_options.html.md.erb @@ -15,6 +15,9 @@ All data that Geode moves out of the local cache must be serializable. However, - Regions that receive events from remote caches - Regions that provide function arguments and results +**Note:** +If you are storing objects with the [HTTP Session Management Modules](../../tools_modules/http_session_mgmt/chapter_overview.html), these objects must be serializable since they are serialized before being stored in the region. + To minimize the cost of serialization and deserialization, Geode avoids changing the data format whenever possible. This means your data might be stored in the cache in serialized or deserialized form, depending on how you use it. For example, if a server acts only as a storage location for data distribution between clients, it makes sense to leave the data in serialized form, ready to be transmitted to clients that request it. Partitioned region data is always initially stored in serialized form. ## <a id="data_serialization_options__section_691C2CF5A4E24D599070A7AADEDF2BEC" class="no-quick-link"></a>Data Serialization Options @@ -36,6 +39,7 @@ Geode Data serialization is about 25% faster than PDX serialization, however usi | Provides single field access of serialized data, without full deserialization - supported also for OQL querying. | Â | X | | Automatically ported to other languages by Geode | Â | X | | Works with .NET clients. | X | X | +| Works with C++ clients. | X | X | | Works with Geode delta propagation. | X | X (See note below.) | <span class="tablecap">**Table 1.** Serialization Options: Comparison of Features</span>
