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

BestPractice-Caching.md #43

Merged
merged 2 commits into from
Aug 9, 2017
Merged

BestPractice-Caching.md #43

merged 2 commits into from
Aug 9, 2017

Conversation

ydfzgyj
Copy link
Collaborator

@ydfzgyj ydfzgyj commented Jul 26, 2017

close #2

jonirrings
jonirrings previously approved these changes Aug 3, 2017
Copy link
Collaborator

@jonirrings jonirrings left a comment

Choose a reason for hiding this comment

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

已校对,无问题

@jonirrings jonirrings changed the title BestPractice-Caching BestPractice-Caching.md Aug 4, 2017
@@ -31,21 +31,21 @@ One possible pattern for this is reserving a field, like `id`, to be a globally
}
```

This is a powerful tool to hand to client developers. In the same way that the URLs of a resource-based API provided a globally unique key, the `id` field in this system provides a globally unique key.
这是向客户端开发人员提供的强大工具。与基于资源的 API 使用 URL 作为全局唯一主键相同的方式,该系统中提供 `id` 字段作为全局唯一主键。
Copy link
Member

Choose a reason for hiding this comment

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

『与基于资源的 API 使用 URL 作为全局唯一主键相同的方式,该系统中提供 id 字段作为全局唯一主键。』=>『与基于资源的 API 使用 URL 作为全局唯一主键的方式相同,该系统中提供 id 字段作为全局唯一主键。』这样是不是读着更通顺一点呢?

@linhe0x0 linhe0x0 merged commit 5d673f8 into xitu:zh-Hans Aug 9, 2017
@ydfzgyj ydfzgyj deleted the best-practice-caching branch August 9, 2017 10:27
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.

BestPractice-Caching.md
3 participants