Yes that would work well. You can always find a completely different way of achieving what you are trying to achieve.
On Saturday, 29 February 2020 18:52:24 UTC+5:30, Jason wrote: > > As said before, you really can't do that too well with celery. Its a good > practice to keep the message body between django -> broker -> worker to be > as small as possible because we don't know what your configuration for the > broker is. In addition, you should never, ever, put sensitive information > in a message, just the identifier of a thing and let celery/django pull > from a data store when the task starts. > > what I would do is save the form data to some intermediate data store, and > pass in the identifier to the celery task for retrieval. That ensures your > data integrity and security is high. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/3f1b4374-ca68-4fcd-a33a-555bc72cbae8%40googlegroups.com.
