You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geode.apache.org by davebarnes97 <gi...@git.apache.org> on 2017/03/18 00:05:46 UTC
[GitHub] geode-native pull request #62: GEODE-2513 Unbrand Connection Pools section o...
GitHub user davebarnes97 opened a pull request:
https://github.com/apache/geode-native/pull/62
GEODE-2513 Unbrand Connection Pools section of docs
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davebarnes97/geode-native feature/GEODE-2513-ConPools
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode-native/pull/62.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #62
----
commit 4c438ddbeadeaa3f3dad734342ecbb8f272f68cd
Author: Dave Barnes <db...@pivotal.io>
Date: 2017-03-17T23:06:28Z
GEODE-2513 Unbrand Connection Pools section of docs
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] geode-native pull request #62: GEODE-2513 Unbrand Connection Pools section o...
Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:
https://github.com/apache/geode-native/pull/62
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] geode-native pull request #62: GEODE-2513 Unbrand Connection Pools section o...
Posted by mmartell <gi...@git.apache.org>.
Github user mmartell commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/62#discussion_r106943344
--- Diff: docs/geode-native-docs/connection-pools/native-client-pool-api.html.md.erb ---
@@ -19,14 +19,14 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-The Geode native client API allows your clients to create and manage connection pools. The server side does not have an API.
+The native client API allows your clients to create and manage connection pools. The server side does not have an API.
This section lists the primary native client API for pool management. For complete information on the classes and interfaces described here, see the API documentation.
**Note:**
Only C\# versions of Pool API interfaces, classes, and methods are shown throughout the text in this section (example: `Pool.GetQueryService()`) . The code examples demonstrate both C++ and C\# versions.
-**Gemstone::GemFire::Cache**
+**Apache.Geode.Cache**
--- End diff --
This should be Apache.Geode.Client.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---
[GitHub] geode-native pull request #62: GEODE-2513 Unbrand Connection Pools section o...
Posted by echobravopapa <gi...@git.apache.org>.
Github user echobravopapa commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/62#discussion_r106952554
--- Diff: docs/geode-native-docs/connection-pools/native-client-pool-api.html.md.erb ---
@@ -19,14 +19,14 @@ See the License for the specific language governing permissions and
limitations under the License.
-->
-The Geode native client API allows your clients to create and manage connection pools. The server side does not have an API.
+The native client API allows your clients to create and manage connection pools. The server side does not have an API.
This section lists the primary native client API for pool management. For complete information on the classes and interfaces described here, see the API documentation.
**Note:**
Only C\# versions of Pool API interfaces, classes, and methods are shown throughout the text in this section (example: `Pool.GetQueryService()`) . The code examples demonstrate both C++ and C\# versions.
-**Gemstone::GemFire::Cache**
+**Apache.Geode.Cache**
--- End diff --
**Apache.Geode.Client.Cache** to be completely clear
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---