Re: Single auth database for multiple (different) django projects

How about Celery & RabbitMQ?

Use Django's signaling functionality to kick off a Celery task, use
Celery to make it async and nearly real-time, then transfer the info
securely.

I recommend *not* allowing the data to be serialized in the RabbitMQ
message (for security & performance), but rather initiate a call to the
other servers via HTTPS or scp with the info, or prompting the other
servers to do a callback to the originating server via HTTPS or scp call
of their own.

Of course, there's no way to avoid race conditions because a person can
be logged into more than one of these apps and once and make changes
nearly simultaneously, but

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to django-users+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.