Implemented in the master
branch, on track for 1.0.
This is the design plan for implementing the ability to revoke a task that has been sent.
We’ll add a broadcast queue:
queue: "celerycast"
exchange: "celerycast"
exchange_type: "fanout"
binding_key: ""
Each worker is listening to this queue, when a message of the following format arrives:
it saves this uuid as revoked, the mediator then skips this message if it ever gets popped off the queue.
To make sure this dict doesn’t grow large, the entries expires after a configurable amount of time.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4