Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

update question-and-answer translation #37

Merged
merged 6 commits into from
Aug 21, 2018
Merged

update question-and-answer translation #37

merged 6 commits into from
Aug 21, 2018

Conversation

DeanLee2013
Copy link
Contributor

No description provided.


```java
CseHttpEntity<xxxx.class> httpEntity = new CseHttpEntity<>(xxx);
//透传内容
//Transparent content
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

透传是传送的意思,不是透明的意思。

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

transparent transmission content?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

可以改为:如何在多个微服务之间传递上下文,透传是中文的说法,应该没必要逐字翻译


# 问题描述: 当服务配置了多个transport的时候,在运行时是怎么选择使用哪个transport的?
# Problem: When the service is configured with multiple transports, how do you choose which transport to use at runtime?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

how do you choose which transport to use at runtime? 好像不是这个意思

@@ -68,23 +67,23 @@ servicecomb:
transport: highway
```

* 当一个微服务producer只开放了highway的endpoint
* When a microservice producer only opens the endpoint of the highway

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

opens -> provided

* consumer进程只部署了highway transport jar,则正常使用higway访问
* consumer进程只部署了RESTful transport jar,则无法访问
* consumer进程同时部署了highway和RESTful transport jar,则正常使用highway访问
  * The consumer process only deploys the highway transport jar, and normally uses higway access.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

上面是endpoint,下面access应该对应是endpoint

@@ -144,47 +143,47 @@ Caused by: java.lang.ClassFormatError: Method "testInherate" in class ? has ille
$ref: "#/definitions/ReponseImpl"
```

# 问题描述:微服务框架服务调用是否使用长连接
# Problem: Does the microservices framework service call use long connections?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

long connections -> long live connection


# 问题描述:服务断连服务中心注册信息是否自动删除
# Problem: Whether the service disconnection service's center registration information is automatically deleted

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这个翻译有点不大通顺?


```
servicecomb:
request:
timeout: 30000
```

# 问题描述:服务治理的处理链顺序是否有要求?
# Problem: Is there a requirement for the processing chain of service governance?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

这个翻译不对,是对顺序是否有要求,不是对治理链有要求


Consumer: loadbalance, tracing-consumer, sla-consumer, bizkeeper-consumer

Provider: tracing-provider, sla-provider, bizkeeper-provider

这种顺序能够满足大多数场景,并且不容易出现不可理解的错误。
This order is sufficient for most scenarios and is not prone to incomprehensible errors.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is not prone to incomprehensible errors ...

@@ -31,51 +31,50 @@ servicecomb:
akskCustomCipher: default
```

可以登陆华为云,在“我的凭证”里面查询到accessKey信息,secretKey由用户自己保存,无法查询。如果忘记相关凭证,可以删除凭证信息,生成新的凭证信息。
You can log in to Huawei Cloud and query the accessKey information in "My Credentials". The secretKey is saved by the user and cannot be queried. If you forget the relevant credentials, you can delete the voucher information and generate new voucher information.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

log in -> login


检查microservice.yaml中的ak/sk配置是否正确。可以登陆华为云,在“我的凭证”里面查询到accessKey信息,secretKey由用户自己保存,无法查询。如果忘记相关凭证,可以删除凭证信息,生成新的凭证信息。
Check if the ak/sk configuration in microservice.yaml is correct. You can log in to Huawei Cloud and query the accessKey information in "My Credentials". The secretKey is saved by the user and cannot be queried. If you forget the relevant credentials, you can delete the voucher information and generate new voucher information.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

voucher information -> credential information,保持一致比较好


Check the version of the service center. You can download the latest version of the service center from the Huawei Cloud official website, or download the latest version of the service center from ServiceComb's official website.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

去掉中英文华为云官网部分




* spring-boot-starter-provider

在Spring Boot中通过@EnableServiceComb启用java chassis的核心功能。这个功能可以用于“JAVA应用方式”和”Web开发方式“。 在”Web开发方式”中,通过spring.main.web-environment=false禁用了Web环境。因此,这个模块主要是解决”JAVA应用方式“的问题。
Enable the core functionality of java chassis via @EnableServiceComb in Spring Boot. This feature can be used for "JAVA application mode" and "Web development mode". In the "Web development method", the web environment is disabled by spring.main.web-environment=false. Therefore, this module is mainly to solve the problem of "JAVA application mode".

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Web development method -> Web development mode

@liubao68 liubao68 merged commit b64ccd5 into apache:master Aug 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants