Couple of bits more ordering docs

CHANGELOG.txt

@@ -1,8 +1,19 @@
+0.9.2 (2016-02-24)
+------------------
+
+* ASGI spec updated to include `order` field for WebSocket messages
+
+* `enforce_ordering` decorator introduced
+
+* DatabaseChannelLayer now uses transactions to stop duplicated messages
+
+
 0.9.1 (2016-02-21)
 ------------------
 
 * Fix packaging issues with previous release
 
+
 0.9 (2016-02-21)
 ----------------
 

docs/getting-started.rst

@@ -446,6 +446,8 @@ listening logic inside the ``chat-messages`` consumer, as every message would
 pass through it.
 
 
+.. _enforcing-ordering:
+
 Enforcing Ordering
 ------------------
 

docs/inshort.rst

@@ -66,6 +66,17 @@ it's designed to allow both easy sharding as well as the ability to run
 separate clusters with their own protocol and worker servers.
 
 
+Why doesn't it use my favourite message queue?
+----------------------------------------------
+
+Channels is deliberately designed to prefer low latency (goal is a few milliseconds)
+and high throughput over guaranteed delivery, which doesn't match some
+message queue designs.
+
+Some features, like :ref:`guaranteed ordering of messages <enforcing-ordering>`,
+are opt-in as they incur a performance hit.
+
+
 Do I need to worry about making all my code async-friendly?
 -----------------------------------------------------------