aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Smeding <tom.smeding@gmail.com>2020-08-08 22:03:23 +0200
committerTom Smeding <tom.smeding@gmail.com>2020-08-08 22:03:23 +0200
commit2adb1181821a534afa76ee7e25f5f44bb6e958c1 (patch)
tree635cc9a06d3e68bbef600a3db0a62e7677b5aa25
parent610e7625c91d40e8212c46705539391aa85f9539 (diff)
protocol: Fix definitions of 'string' and 'word'
-rw-r--r--protocol.md11
1 files changed, 6 insertions, 5 deletions
diff --git a/protocol.md b/protocol.md
index ff6651b..71fee05 100644
--- a/protocol.md
+++ b/protocol.md
@@ -10,11 +10,12 @@ both client->server and server->client, always ends with a newline (ASCII 10)
character.
Preliminary definitions:
-- A _string_ is a series of non-zero bytes. To allow for clients written in
- languages that automatically parse strings as UTF-8, argument strings should
- always be valid UTF-8. However, the server currently does not care.
-- A _word_ is a string without spaces (ASCII 32) or newlines. Note that the
- empty string is also a valid word.
+- A _string_ is a series of non-zero bytes that are not newlines (ASCII 10). To
+ allow for clients written in programming languages that automatically parse
+ strings as UTF-8, argument strings should always be valid UTF-8. However, the
+ server currently does not care.
+- A _word_ is a string without spaces (ASCII 32) (and also without newlines).
+ Note that the empty string is also a valid word.
There are three kinds of messages: commands from the client, command responses
from the server, and push messages from the server (not to be confused with push