Andrew Godwin

Hm, interesting. I suspect whoever initially wrote this didn't test the `reset()` usage, then, and instead were just trying to persist values inside. Unless you want to dive into this...

Yes, this is a bug. There's likely also a "bug" in the Channels routing code, in that it does not respect the root_path value but instead patches on the raw...

I wanted to try and avoiding overloading the `receive` and `disconnect` channels with information, but I agree, `path_info` would be better to have than `root_path` given the circumstances. (Since you...

Yes, that looks like the same issue. For now the workaround is as you showed with the URL config; you could move the prefix part into a setting, maybe, and...

I'll try to look into this in the next couple of weeks.

There isn't one of these, and I do agree there should be - I've usually called these "acceptance" or "compliance" test suites, and it would help a lot in enforcing...

I agree, it would be helpful, this wouldn't be too hard for someone to write a patch for.

There's no specific reason, but it's so the names can be more easily portable across different backends. Unlimited length names would be hard to deal with in some places.

I don't believe I have an opinion on this, thinking about it - it doesn't really matter, since the server will exit anyway (though most provide a grace period to...

Can I get a bit more clarification if you can? * Is this posting to a Django view or a custom consumer? * Does it happen with all file sizes?...