Ryan Petrello 45819f6b9a requeue websocket messages that don't (yet) have an established user ...

There's a race between our `ws_connect` and `ws_receive` methods;
it's possible to fall into a scenario where we're handling a legitimate
message *before* django-channels is able to persist the `user_id` into
the channel session.  This results in a scenario where a user can open
a browser tab and never receive new websocket messages.  In this
scenario, we should just toss the message back into the queue and try
again later (up to a reasonable limit of retries).

2017-02-28 11:12:59 -05:00

..

__init__.py

fixed copyright date

2015-06-11 16:10:23 -04:00

defaults.py

requeue websocket messages that don't (yet) have an established user

2017-02-28 11:12:59 -05:00

development_quiet.py

remove statsd

2016-05-10 11:56:04 -04:00

development.py

move reload functionality to its own file

2017-02-15 13:42:49 -05:00

local_settings.py.docker_compose

Set TIME_ZONE to None.

2017-01-10 10:51:23 -05:00

local_settings.py.example

Set TIME_ZONE to None.

2017-01-10 10:51:23 -05:00

production.py

move reload functionality to its own file

2017-02-15 13:42:49 -05:00