From eed6e5e607d36851ab3d5fbbf09994495abb8f00 Mon Sep 17 00:00:00 2001 From: Andrew Godwin Date: Wed, 9 Sep 2015 22:07:52 -0500 Subject: [PATCH] Don't waffle about ordering guarantees --- docs/message-standards.rst | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/message-standards.rst b/docs/message-standards.rst index 722e218..8924048 100644 --- a/docs/message-standards.rst +++ b/docs/message-standards.rst @@ -11,8 +11,7 @@ In addition to the standards outlined below, each message may contain a separate connection and data receiving messages (like WebSockets) will only contain the connection and detailed client information in the first message; use the ``@channel_session`` decorator to persist this data to consumers of -the received data (the decorator will take care of handling persistence and -ordering guarantees on messages). +the received data (or something else based on ``reply_channel``). All messages must be able to be encoded as JSON; channel backends don't necessarily have to use JSON, but we consider it the lowest common denominator