You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicecomb.apache.org by ni...@apache.org on 2019/09/06 15:58:21 UTC
[servicecomb-docs] branch master updated (8be6b7d -> 2080fc0)
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git.
from 8be6b7d [SCB-1462] modify descriptions of servicecomb.service.registry.client.eventLoopPoolSize and servicecomb.service.registry.client.workerPoolSize
new 0742bf3 Update interface-constraints.md
new 2080fc0 Update interface-constraints.md
The 2 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
Summary of changes:
java-chassis-reference/en_US/build-provider/interface-constraints.md | 2 +-
java-chassis-reference/zh_CN/build-provider/interface-constraints.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
[servicecomb-docs] 01/02: Update interface-constraints.md
Posted by ni...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git
commit 0742bf38cc795fb89c421fcf2d60df70fb0e208c
Author: 自然 <na...@qq.com>
AuthorDate: Fri Sep 6 19:55:02 2019 +0800
Update interface-constraints.md
---
java-chassis-reference/en_US/build-provider/interface-constraints.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/java-chassis-reference/en_US/build-provider/interface-constraints.md b/java-chassis-reference/en_US/build-provider/interface-constraints.md
index c00e402..3506603 100644
--- a/java-chassis-reference/en_US/build-provider/interface-constraints.md
+++ b/java-chassis-reference/en_US/build-provider/interface-constraints.md
@@ -8,7 +8,7 @@ For example:
```java
public Person query(String id);
public Object query(String id);
-public class Person {String name;}
+public Person query(String name);
```
Obviously, if API 1 is called, we know that an ID parameter of String type needs to be transferred. The returned value is of Person type, which contains a string-typed name parameter. If API 2 is called, we do not know how to process the returned value, and need to refer to documents provided by the service provider. API 2 is developed in the perspective of RPC developers.
[servicecomb-docs] 02/02: Update interface-constraints.md
Posted by ni...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
ningjiang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/servicecomb-docs.git
commit 2080fc0ebd3a8e7e876370e40982d85dc26b4e1a
Author: 自然 <na...@qq.com>
AuthorDate: Fri Sep 6 19:58:19 2019 +0800
Update interface-constraints.md
---
java-chassis-reference/zh_CN/build-provider/interface-constraints.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/java-chassis-reference/zh_CN/build-provider/interface-constraints.md b/java-chassis-reference/zh_CN/build-provider/interface-constraints.md
index a8e768a..7e6c119 100644
--- a/java-chassis-reference/zh_CN/build-provider/interface-constraints.md
+++ b/java-chassis-reference/zh_CN/build-provider/interface-constraints.md
@@ -9,7 +9,7 @@ ServiceComb-Java-Chassis建议接口定义遵循一个简单的原则：接口
```java
public Person query(String id);
public Object query(String id);
-public class Person {String name;}
+public Person query(String name);
```
显然调用接口一，我们知道要传递一个String类型的id参数，返回值是一个Person类型，Person里面存在String类型的name参数。调用接口二，我们不知道怎么处理返回值，必须参考服务提供者的文档说明。这个视角是熟练的RPC开发者的视角。