The thing is, you will then be doing it synchronously, because python's
global interpreter lock means that threads are never really parallel.
To avoid having the sensitive data in your celery queues, have your task
retrieve the sensitive data from the database (if that's where its coming
from). If it's coming from the frontend, then you are going to have to
store it somewhere if you want to do this asynchronously. I doubt that
poses such a great additional security risk, as long as it all remains on
the same machine, especially if you use a volatile celery backend (e.g.
redis with no persistence enabled).
If you are doing it synchronously, then you may want to consider if the
client can pass you the data via an ajax call from a web worker, which will
improve the user perception of performance.
On Fri, May 11, 2012 at 11:17 AM, Thomas Orozco
Tel: 07773 787 105