Can we use Redis stream with django-event-stream for deliverability

[pushkarcodes110]

I dont know if there is default throttling that comes with package, but this is what i found some inconsistency when triggering multiple send_events at a given time. i tried triggering view which has send_event function 5 times continuously and i got only 2 out of 5 SSE in my connected channel.

Well, i want to make this with at most delivery, so i am thinking f using redis stream, so instead of directly sending SSE from view. I will first store it in redis stream and i will set a worker in a loop which listens to any events and executes them.
i might also figure this out if i want to check if SSE failed due to client disconnection or any network error. i want to save that event and retry again when clients connect back.

but this seems a lot of work actually, so if anyone have better approach, I am all ears.

[jkarneges]

Reliable delivery is achieved with event storage. The default DjangoModelStorage class stores messages in the SQL database and expires them after 24 hours. There is also now a RedisStorage class, for using Redis instead of the SQL database. It does not use Redis streams though.

The way storage works is send_event() first places an event in storage and then attempts delivery to the clients. If a client's queue is full, delivery will be retried later. If a client gets disconnected, delivery will be retried when the client reconnects. There is no need to set up an extra worker to do redeliveries.