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.

Sign up for GitHub

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

Jump to bottom

2.2: Should v. Must #13

Open
milesmcc opened this issue Apr 14, 2019 · 0 comments
Open

2.2: Should v. Must #13

milesmcc opened this issue Apr 14, 2019 · 0 comments

Comments

@milesmcc
Copy link
Contributor

According to a friend of @micahflee, the SHOULD in section 2.2 might be better as a MUST:

To perform an update, the client MUST perform the following steps on
each keylist to which it is subscribed. The steps SHOULD be performed
in the given order.

Steps 3 and 4 might be interchangeable, but every other step must be done in order. We might as well set it in stone...
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@milesmcc