From 6e8cbb1eba3db44606e683daea47e2a23d603a42 Mon Sep 17 00:00:00 2001
From: Kegsay <kegsay@gmail.com>
Date: Wed, 31 Dec 2014 13:53:45 +0000
Subject: [PATCH] Small HTTP note on message ordering

---
 drafts/general_api.rst | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/drafts/general_api.rst b/drafts/general_api.rst
index 1644adad..cb005b00 100644
--- a/drafts/general_api.rst
+++ b/drafts/general_api.rst
@@ -255,6 +255,10 @@ Outputs:
  - When in the stream this action happened. (to correctly display local echo)
 What data flows does it address:
  - Chat Screen: Send a Message
+Ordering notes:
+ - HTTP: When sending a message with a higher seqnum, it will block the request until it receives 
+   earlier seqnums. The block will expire after a timeout and reject the message stating that it 
+   was missing a seqnum.
 E2E Notes:
  - For signing: You send the original message to the HS and it will return the full event JSON which will
    be sent. This full event is then signed and sent to the HS again to send the message.