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/20 22:52:19 UTC
[GitHub] geode-native pull request #64: GEODE-2513 Unbrand geode-native docs: Continu...
GitHub user davebarnes97 opened a pull request:
https://github.com/apache/geode-native/pull/64
GEODE-2513 Unbrand geode-native docs: Continuous Query
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/davebarnes97/geode-native feature/GEODE-2513-CQ
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/geode-native/pull/64.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 #64
----
commit f23911f4b3252562a6b4a6f92f7036b9329c36f1
Author: Dave Barnes <db...@pivotal.io>
Date: 2017-03-20T22:49:50Z
GEODE-2513 Unbrand geode-native docs: Continuous Query
----
---
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 #64: GEODE-2513 Unbrand geode-native docs: Continu...
Posted by pivotal-jbarrett <gi...@git.apache.org>.
Github user pivotal-jbarrett commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/64#discussion_r107045279
--- Diff: docs/geode-native-docs/continuous-querying/3-native-client-cq-api.html.md.erb ---
@@ -21,9 +21,10 @@ limitations under the License.
This chapter documents the primary native client API for CQ management.
-The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here, see the API documentation at [http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io).
+The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here,
+see the API documentation for [C++](/releases/latest/api/cppdocs) or [C\#](/releases/latest/api/dotnetdocs).
-**Gemstone::GemFire::Cache**
+**Apache.Geode.Client.Cache**
--- End diff --
Cool beans!
---
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 #64: GEODE-2513 Unbrand geode-native docs: Continu...
Posted by pivotal-jbarrett <gi...@git.apache.org>.
Github user pivotal-jbarrett commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/64#discussion_r107040822
--- Diff: docs/geode-native-docs/continuous-querying/3-native-client-cq-api.html.md.erb ---
@@ -21,9 +21,10 @@ limitations under the License.
This chapter documents the primary native client API for CQ management.
-The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here, see the API documentation at [http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io).
+The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here,
+see the API documentation for [C++](/releases/latest/api/cppdocs) or [C\#](/releases/latest/api/dotnetdocs).
-**Gemstone::GemFire::Cache**
+**Apache.Geode.Client.Cache**
--- End diff --
Why switch from the C++ notation to the C# notation?
---
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 #64: GEODE-2513 Unbrand geode-native docs: Continu...
Posted by karensmolermiller <gi...@git.apache.org>.
Github user karensmolermiller commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/64#discussion_r107041831
--- Diff: docs/geode-native-docs/continuous-querying/3-native-client-cq-api.html.md.erb ---
@@ -21,9 +21,10 @@ limitations under the License.
This chapter documents the primary native client API for CQ management.
-The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here, see the API documentation at [http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io).
+The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here,
+see the API documentation for [C++](/releases/latest/api/cppdocs) or [C\#](/releases/latest/api/dotnetdocs).
--- End diff --
Would it be better to use ".NET" instead of "C#" (in both files with these links)?
---
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 #64: GEODE-2513 Unbrand geode-native docs: Continu...
Posted by davebarnes97 <gi...@git.apache.org>.
Github user davebarnes97 commented on a diff in the pull request:
https://github.com/apache/geode-native/pull/64#discussion_r107042429
--- Diff: docs/geode-native-docs/continuous-querying/3-native-client-cq-api.html.md.erb ---
@@ -21,9 +21,10 @@ limitations under the License.
This chapter documents the primary native client API for CQ management.
-The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here, see the API documentation at [http://gemfire-apis.docs.pivotal.io](http://gemfire-apis.docs.pivotal.io).
+The Apache Geode native client API allows your clients to create and manage CQs. (The server side does not have an API.) Continuous querying provides native client query syntax, events-based management, integration with client/server architecture, active query execution, and interest criteria based on data values. For complete information on the classes and interfaces described here,
+see the API documentation for [C++](/releases/latest/api/cppdocs) or [C\#](/releases/latest/api/dotnetdocs).
-**Gemstone::GemFire::Cache**
+**Apache.Geode.Client.Cache**
--- End diff --
The preceding text says it will be using C# notation, so it should have been C# all along.
---
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.
---