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

Corrected minor typos in spec.md #32

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Corrected minor typos in spec.md #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions spec.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -171,7 +171,7 @@ The following are the types implemented by RESP3:
* Map: an ordered collection of key-value pairs. Keys and values can be any other RESP3 type.
* Set: an unordered collection of N other types.
* Attribute: Like the Map type, but the client should keep reading the reply ignoring the attribute type, and return it to the client as additional information.
* Push: Out of band data. The format is like the Array type, but the client should just check the first string element, stating the type of the out of band data, a call a callback if there is one registered for this specific type of push information. Push types are not related to replies, since they are information that the server may push at any time in the connection, so the client should keep reading if it is reading the reply of a command.
* Push: Out of band data. The format is like the Array type, but the client should just check the first string element, stating the type of the out of band data, and call a callback if there is one registered for this specific type of push information. Push types are not related to replies, since they are information that the server may push at any time in the connection, so the client should keep reading if it is reading the reply of a command.
* Hello: Like the Map type, but is sent only when the connection between the client and the server is established, in order to welcome the client with different information like the name of the server, its version, and so forth.
* Big number: a large number non representable by the Number type

Expand Down Expand Up @@ -761,7 +761,7 @@ has the following format:
.<CR><LF>

Unbound Sets are exactly like Arrays with the difference that the transfer
wills tart with `~` instead of `*` character. However with the Map type
will start with `~` instead of `*` character. However with the Map type
things are marginally different: the program emitting the protocol *must*
make sure that it emits an even number of elements, since every couple
represents a field-value pair:
Expand Down