-
Notifications
You must be signed in to change notification settings - Fork 198
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Co-authored-by: sevdog <[email protected]>
- Loading branch information
1 parent
13cef45
commit 966641f
Showing
6 changed files
with
371 additions
and
75 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -171,6 +171,7 @@ to 10, and all ``websocket.send!`` channels to 20: | |
If you want to enforce a matching order, use an ``OrderedDict`` as the | ||
argument; channels will then be matched in the order the dict provides them. | ||
|
||
.. _encryption | ||
``symmetric_encryption_keys`` | ||
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
|
@@ -237,6 +238,52 @@ And then in your channels consumer, you can implement the handler: | |
async def redis_disconnect(self, *args): | ||
# Handle disconnect | ||
``serializer_format`` | ||
~~~~~~~~~~~~~~~~~~~~~~ | ||
|
||
By default every message sent to redis is encoded using `msgpack <https://msgpack.org/>`_ (_currently ``msgpack`` is a mandatory dependency of this package, it may become optional in a future release_). | ||
It is also possible to switch to `JSON <http://www.json.org/>`_: | ||
|
||
.. code-block:: python | ||
CHANNEL_LAYERS = { | ||
"default": { | ||
"BACKEND": "channels_redis.core.RedisChannelLayer", | ||
"CONFIG": { | ||
"hosts": ["redis://:[email protected]:6379/0"], | ||
"serializer_format": "json", | ||
}, | ||
}, | ||
} | ||
Custom serializers can be defined by: | ||
|
||
- extending ``channels_redis.serializers.BaseMessageSerializer``, implementing ``as_bytes `` and ``from_bytes`` methods | ||
- using any class which accepts generic keyword arguments and provides ``serialize``/``deserialize`` methods | ||
|
||
Then it may be registered (or can be overriden) by using ``channels_redis.serializers.registry``: | ||
|
||
.. code-block:: python | ||
from channels_redis.serializers import registry | ||
class MyFormatSerializer: | ||
def serialize(self, message): | ||
... | ||
def deserialize(self, message): | ||
... | ||
registry.register_serializer('myformat', MyFormatSerializer) | ||
**NOTE**: the registry allows you to override the serializer class used for a specific format without any check nor constraint. Thus it is recommended that to pay particular attention to the order-of-imports when using third-party serializers which may override a built-in format. | ||
|
||
|
||
Serializers are also responsible for encryption using *symmetric_encryption_keys*. When extending ``channels_redis.serializers.BaseMessageSerializer`` encryption is already configured in the base class, unless you override the ``serialize``/``deserialize`` methods: in this case you should call ``self.crypter.encrypt`` in serialization and ``self.crypter.decrypt`` in deserialization process. When using a fully custom serializer, expect an optional sequence of keys to be passed via ``symmetric_encryption_keys``. | ||
|
||
|
||
Dependencies | ||
------------ | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.