Dark-Alex-17/kapow
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Minor fixes on human words.

Browse Source 
Thanks-to: Nilp0inter
This commit is contained in:
César Gallego Rodríguez
2019-08-21 12:01:08 +02:00
parent 9ef714309d
commit 3a8adb19f7
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
spec/README.md
+3 -3
View File
@@ -127,18 +127,18 @@ whole lifetime of the server.
## Design Principles ## Design Principles
* TCP implementations should follow a general principle of robustness: be * Kapow! implementations should follow a general principle of robustness: be
conservative in what you do, be liberal in what you accept from others. conservative in what you do, be liberal in what you accept from others.
* We reuse conventions of well-established software projects, such as Docker. * We reuse conventions of well-established software projects, such as Docker.
* All requests and responses will leverage JSON as the data encoding method. * All requests and responses will leverage JSON as the data encoding method.
* The API calls responses will several parts: * The API calls responses have several parts:
* The HTTP status code (e.g., `400`, which is a bad request). The target * The HTTP status code (e.g., `400`, which is a bad request). The target
audience of this information is the client code. The client can thus use audience of this information is the client code. The client can thus use
this information to control the program flow. this information to control the program flow.
* The HTTP reason phrase. The target audience in this case is the human * The HTTP reason phrase. The target audience in this case is the human
operating the client. The human can use this information to make a operating the client. The human can use this information to make a
decision on how to proceed. decision on how to proceed.
* The body it's optional * The body is optional
* All successful API calls will return a representation of the *final* state * All successful API calls will return a representation of the *final* state
attained by the objects which have been addressed (either requested, set or attained by the objects which have been addressed (either requested, set or
deleted). deleted).