| From: | Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com> |
|---|---|
| To: | Jan Urbański <wulczer(at)wulczer(dot)org> |
| Cc: | Tobias Oberstein <tobias(dot)oberstein(at)tavendo(dot)de>, "psycopg(at)postgresql(dot)org" <psycopg(at)postgresql(dot)org> |
| Subject: | Re: NOTIFY in asynchronous mode |
| Date: | 2011-11-06 10:42:34 |
| Message-ID: | CA+mi_8ZOnbNEBxhdBVeY8riB_DP+nFRGfG4vZMmBW3MzsiTgGg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | psycopg |
On Nov 5, 2011 12:21 AM, "Jan Urbański" <wulczer(at)wulczer(dot)org> wrote:
>
> On 05/11/11 01:15, Daniele Varrazzo wrote:
> > Is it possible to use a naked psycopg connection instead of tx? I
> > mean, not for the regular query-return cycle, but just for sitting
> > idle in the reactor and get a callback called upon notify.
>
> Not in an easy way, I'm afraid. Stuff put in the reactor as readers need
> to implement the IReadDescriptor interface[0] which means you'd have to
> wrap the connection object with something that proxies fileno() to the
> connection and looks for notifies when doRead() is called on it.
Doh, sorry if I made it too easy. It would be great if notifies could
be used easily from Twisted: they seem made for each other like bread
and nutella. Please keep us informed if you manage to add the support
to the library.
Comparatively, receiving notifies in greenlet environments is
straightforward:
<http://initd.org/psycopg/articles/2010/12/01/postgresql-notifications-psycopg2-eventlet/>.
-- Daniele
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Urbański | 2011-11-06 20:54:42 | Re: NOTIFY in asynchronous mode |
| Previous Message | Tobias Oberstein | 2011-11-05 12:37:39 | Re: NOTIFY in asynchronous mode |