mirror of https://github.com/zulip/zulip.git
b9ec2545bb
This is a fairly risky, invasive change that speeds up stream deactivation by no longer sending subscription/remove events for individual subscribers to all of the clients who care about a stream. Instead, we let the client handle the stream deactivation on a coarser level. The back end changes here are pretty straightforward. On the front end we handle stream deactivations by removing the stream (as needed) from the streams sidebar and/or the stream settings page. We also remove the stream from the internal data structures. There may be some edge cases where live updates don't handle everything, such as if you are about to compose a message to a stream that has been deactivated. These should be rare, as admins generally deactivate streams that have been dormant, and they should be recoverable either by getting proper error handling when you try to send to the stream or via reload. |
||
---|---|---|
.. | ||
fixtures | ||
lib | ||
management | ||
migrations | ||
templatetags | ||
tests | ||
tornado | ||
views | ||
webhooks | ||
worker | ||
__init__.py | ||
apps.py | ||
context_processors.py | ||
decorator.py | ||
exceptions.py | ||
filters.py | ||
forms.py | ||
logging_handlers.py | ||
middleware.py | ||
models.py | ||
static_header.txt | ||
storage.py |