Is your feature request related to a problem? Please describe.
I wonder if the publish/subscribe pattern is in the range of Flower features ?
My use case includes communication from a frontend web application to Flower API so I can get the list of pending/success/failed tasks.
Now I'm trying to refresh the list when a task has finished or failed. And I would like to avoid such things as setInterval() methods on JS side.
Did anybody already try to implement such message broadcast ? Or should I rather look into Django channels and websockets ?
Describe the solution you'd like
Some sort of pub/sub pattern attached to the Flower REST API.
I read on other issues that websocket was removed from Flower code, so I would like to know if we can expect this pub/sub pattern in Flower in future releases or if this is definitely not on the development roadmap ?
Is your feature request related to a problem? Please describe.
I wonder if the publish/subscribe pattern is in the range of Flower features ?
My use case includes communication from a frontend web application to Flower API so I can get the list of pending/success/failed tasks. Now I'm trying to refresh the list when a task has finished or failed. And I would like to avoid such things as
setInterval()methods on JS side. Did anybody already try to implement such message broadcast ? Or should I rather look into Django channels and websockets ?Describe the solution you'd like
Some sort of pub/sub pattern attached to the Flower REST API. I read on other issues that websocket was removed from Flower code, so I would like to know if we can expect this pub/sub pattern in Flower in future releases or if this is definitely not on the development roadmap ?