1👍
✅
As a general rule (with all background tasks, not just Celery/Django) that’s actually your best bet. The same pattern emerges
- User makes HTTP request
- Server kicks off background service (either through Celergy, some other async. service, or even through a command line execution (<- don’t do that if you can avoid it)) and returns some form of identifier
- User agent makes new HTTP request to get information about state of new service/process.
You should check out long polling
Source:stackexchange.com