#25669: Adding postgresql publish/subscribe mechanism to django postgres contrib
module
----------------------------------+--------------------------------------
Reporter: auvipy | Owner: auvipy
Type: New feature | Status: assigned
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
Keywords: postgres, pubsub | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+--------------------------------------
Comment (by jarshwah):
How would you envisage this working? Can you describe a use case that
would make sense for Django?
I can probably think of a couple once/if Andrew Godwin finishes off his
work with Channels: https://www.aeracode.org/2015/6/17/beyond-request-
response/
But I can't think of any use cases that would be tied to the regular
request/response cycle. This would probably be something better
implemented as a third party library in any case, or as a backend for
something like django-celery.
--
Ticket URL: <https://code.djangoproject.com/ticket/25669#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/064.0951a3474581f1dd1992b931ba92eb58%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
