--
Ticket URL: <https://code.djangoproject.com/ticket/25669>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
* status: new => assigned
* owner: => auvipy
* needs_docs: => 0
* needs_tests: => 0
* needs_better_patch: => 0
--
Ticket URL: <https://code.djangoproject.com/ticket/25669#comment:1>
Old description:
New description:
It will be great to have postgresql's pub/sub mechanism in
django.contrib.postgres
--
--
Ticket URL: <https://code.djangoproject.com/ticket/25669#comment:2>
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>
Comment (by auvipy):
Hi,
based on the works here https://bitbucket.org/btubbs/pgpubsub/overview and
postgres built in pub/sub mechanism wouldn't it good to have implemented
in model based pub/sub functionality in contrib.postgres?
--
Ticket URL: <https://code.djangoproject.com/ticket/25669#comment:4>
* status: assigned => closed
* resolution: => needsinfo
Comment:
Could you please detail the API you have in mind and raise it on the
DevelopersMailingList to get consensus on the idea?
--
Ticket URL: <https://code.djangoproject.com/ticket/25669#comment:5>