From ccad3d8e2f829f5a3be9a969fc69ea5125e02a64 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pau=20Ru=C5=80lan?= Date: Mon, 14 Dec 2015 10:29:10 +0100 Subject: [PATCH] add question about messagepack in faq from request #37 --- docs/faqs.rst | 16 ++++++++++++++++ 1 file changed, 16 insertions(+) diff --git a/docs/faqs.rst b/docs/faqs.rst index 21e8caf..cbc0635 100755 --- a/docs/faqs.rst +++ b/docs/faqs.rst @@ -124,3 +124,19 @@ You can also provide your own solution if you wish, keyed off of ``message.reply which is the unique channel representing the connection, but remember that whatever you store in must be **network-transparent** - storing things in a global variable won't work outside of development. + + +Would you support messagepack or any other format? +-------------------------------------------------- + +Although we've evaluated msgpack it does not offer enough over JSON to be +reasonable - the encoding/decoding is often slower, the language support is +much poorer, and in general we would rather just have one version of a standard, +especially since there's plans to write parts of the Channels system in other +languages. + +That said, at some point it's up to the individual channel backend to support +whatever it likes, as long as it spits out dicts at either end. So this is +something that could be implemented by someone else as a pluggable backend to +see. We might always come back and revisit this if message size/bandwidth turns +out to be a limiting factor, though.