Justin Karneges

Great to see this, Z. At the high level, I'd change "Server-Sent Events" to simply "Streaming", as SSE is just one type of streaming format in the wild and you'll...

You might enjoy the WebSockHop client library: https://github.com/fanout/websockhop It speaks pure WebSocket protocol (nothing special needed on the server) and handles automatic reconnect as well as message timeouts.

A header would be the ideal way, but I don't think a header can be set in all cases (e.g. jsonp, websockets), so a fallback would be needed.

Pushpin does support the `/info` endpoint, but this is also too ambiguous to match all paths on. Can't just hijack all GET requests to URIs ending with /info under the...

Hmm, that line doesn't seem to be in the codebase. If it's from a stack trace, do you have more of it?

I wonder if this is a dependency versions problem. Here's what is used by the chat example in this repo: https://github.com/fanout/django-eventstream/blob/master/examples/chat/requirements.txt You could try pinning to the same versions and...

No idea. A reproducible example would help. Maybe apply your middleware to the chat example?

I think it's unintentional. There's already `EVENT_TRIM_BATCH` to limit the size of the bulk deletes. PR welcome. :)

Hmm, I suspect a transaction blocking problem. Can you reproduce this with the chat example?

It looks like `extra_requires` could be used to specify channels as an optional dependency, that would only be installed if the user asks for it (for example by specifying a...