Motivation
Currently all anonymisation requests are received by the orthanc plugin and just queued in memory. This means that we can't drain the queue if we want to stop processing images.
Pitch
Create a rabbitmq queue for anonymisation requests. I don't think there's a way to get the orthanc plugin to passively consume from a queue, so expect we may publish to the queue, and then have the thread in the pixl plugin in orthanc anon to consume from the queue until there are no messages left
Alternatives
No response
Additional context
Looking at the existing queue implementation may be useful as a reference: https://github.com/SAFEHR-data/PIXL/tree/main/pixl_core/src/core/patient_queue
We also don't need to faff around with async publishing or consuming, or token buckets etc.
For now don't pass through message priority, we can add this if we ever decide we need it
out of scope
Changing the processing to slave worker processes
Acceptance
Motivation
Currently all anonymisation requests are received by the orthanc plugin and just queued in memory. This means that we can't drain the queue if we want to stop processing images.
Pitch
Create a rabbitmq queue for anonymisation requests. I don't think there's a way to get the orthanc plugin to passively consume from a queue, so expect we may publish to the queue, and then have the thread in the pixl plugin in orthanc anon to consume from the queue until there are no messages left
Alternatives
No response
Additional context
Looking at the existing queue implementation may be useful as a reference: https://github.com/SAFEHR-data/PIXL/tree/main/pixl_core/src/core/patient_queue
We also don't need to faff around with async publishing or consuming, or token buckets etc.
For now don't pass through message priority, we can add this if we ever decide we need it
out of scope
Changing the processing to slave worker processes
Acceptance