Re: Channels: startup order of daphne and workers leads to issues

Hi Alex, It sounds like this isn't a daphne/workers ordering bug (things just queue and run when available) but a serialisability issue - that is, you expected `websocket.connect` to run before `websocket.receive` but in the released version they will run in parallel if both have queued messages.

Channels: startup order of daphne and workers leads to issues

Hello, I noticed a weird thing during a deployment of a service that uses channels at work the other day. We use docker, so we have a container for daphne and a container for workers (currently 4). We start a service that some other machines connect to almost automatically (reconnecting etc), a