Django-websocket-redis3

Latest version: v0.4.4.1

Safety actively analyzes 629723 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 2 of 3

0.3.1

-----
* Keys for entries in Redis datastore can be prefixed by an optional string. This may be required
to avoid namespace clashes.

0.3.0

-----
* Added possibility to publish and subscribe for Django Groups, additionally to Users and Sesions.
* To ease the communication between Redis and the Django, a new class ``RedisPublisher`` has
been added as Programming Interface for the Django loop. Before, one had to connect to the Redis
datastore directly to send messages to the Websoclet loop.
* Renamed configuration setting ``WS4REDIS_STORE`` to ``WS4REDIS_SUBSCRIBER``.

0.2.3

-----
* Fixed: Use flush to discard received PONG message.

0.2.2

-----
* Moved mokey patching for Redis socket into the runner. This sometimes caused errors when
running in development mode.
* Added timeout to select call. This caused IOerrors when running under uWSGI and the websocket
was idle.

0.2.1

-----
* Reverted issue 1 and dropped compatibility with Django-1.4 since the response status must
use force_str.

0.2.0

-----
* Major API changes.
* Use ``WS4REDIS_...`` in Django settings.
* Persist messages, allowing server reboots and reconnecting the client.
* Share the file descriptor for Redis for all open connections.
* Allow to override the subscribe/publish engine.

Page 2 of 3

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.