From c834bd44479283dbb3438ba422fbb06ea094af4c Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?C=C3=A9sar=20Gallego=20Rodr=C3=ADguez?= Date: Wed, 21 Aug 2019 09:57:44 +0200 Subject: [PATCH] Robustness principle and optional body. --- spec/README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/spec/README.md b/spec/README.md index a8928b9..7fd5436 100644 --- a/spec/README.md +++ b/spec/README.md @@ -126,15 +126,18 @@ whole lifetime of the server. ## Design Principles +* TCP implementations should follow a general principle of robustness: be + conservative in what you do, be liberal in what you accept from others. * We reuse conventions of well-established software projects, such as Docker. * All requests and responses will leverage JSON as the data encoding method. -* The API calls responses will have two distinct parts: +* The API calls responses will several parts: * 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 this information to control the program flow. * 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 decision on how to proceed. + * The body it's optional * All successful API calls will return a representation of the *final* state attained by the objects which have been addressed (either requested, set or deleted).