From b296fee4c7958b74f49576ea8550e81e2f1eb791 Mon Sep 17 00:00:00 2001 From: Cory Benfield Date: Thu, 10 Mar 2016 09:57:33 +0000 Subject: [PATCH] Be a bit clearer about guaranteed ordering. --- docs/asgi.rst | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/docs/asgi.rst b/docs/asgi.rst index 61c0cfa..d9a4f6d 100644 --- a/docs/asgi.rst +++ b/docs/asgi.rst @@ -766,11 +766,13 @@ a very good performance or implementation reason is present: handle these within the protocol server and don't expose them in ASGI messages. -* If the protocol has guaranteed ordering, ASGI messages should include an - ``order`` field (0-indexed) that preserves the ordering as received by the - protocol server (or as sent by the client, if available). This ordering should - span all message types emitted by the client - for example, a connect message - might have order ``0``, and the first two frames order ``1`` and ``2``. +* If the protocol has guaranteed ordering and does not use a specific channel + for a given connection (as HTTP does for body data), ASGI messages should + include an ``order`` field (0-indexed) that preserves the ordering as + received by the protocol server (or as sent by the client, if available). + This ordering should span all message types emitted by the client - for + example, a connect message might have order ``0``, and the first two frames + order ``1`` and ``2``. * If the protocol is datagram-based, one datagram should equal one ASGI message (unless size is an issue)