From 701c8add0d75f94ca2c34cafa686a54aee5854c6 Mon Sep 17 00:00:00 2001 From: Tom Smeding Date: Mon, 27 Jul 2020 16:02:21 +0200 Subject: Fix docs: 'history' gives messages in chronological order --- protocol.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'protocol.md') diff --git a/protocol.md b/protocol.md index 346bfe4..ac8d86a 100644 --- a/protocol.md +++ b/protocol.md @@ -55,11 +55,11 @@ A _response_ from the server will be in one of the following forms: - ` history ` - Response to the client's `history` command; is followed by exactly `` messages of type `history_message` with the same tag. The messages are - returned in reverse chronological order (newest first). + returned in chronological order (oldest first). - ` history_message ` - Part of the response to the client's `history` command. Index 0 is the - newest message; index (`` - 1) (from the `history` response) is the - oldest message in the fragment requested. Timestamps are microseconds since + oldest message; index (`` - 1) (from the `history` response) is the + newest message in the fragment requested. Timestamps are microseconds since the UNIX epoch. The message id for each message is globally unique for the entire server. @@ -136,7 +136,7 @@ ranges until the end of the line). member of the room. In the `history` response, `` will be at most ``, and may be less if the room does not yet have `` messages. Each message will be returned in a `history_message` response - after the `history` response, in reverse chronological order. + after the `history` response, in chronological order. - Returns `history`, followed by zero or more `history_message`. - ` history_before ` - Same as `history`, except the returned messages are the last `` -- cgit v1.2.3-54-g00ecf