| From: | Andras Kadinger <bandit(at)surfnonstop(dot)com> |
|---|---|
| To: | pgsql-jdbc(at)postgresql(dot)org |
| Subject: | Re: implementing asynchronous notifications |
| Date: | 2005-04-11 03:51:29 |
| Message-ID: | Pine.LNX.4.44.0504110548390.13042-200000@ns.surfnonstop.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-jdbc |
On Mon, 11 Apr 2005, Andras Kadinger wrote:
> I am unclear as to how to handle possible protocol errors (e.g. when what
> we end up reading from the connection is not an 'A'sync Notify).
> Theoretically, in a working connection this should not happen though.
Yes, it could: reading the PostgreSQL protocol documentation, it says
"frontends should always be prepared to accept and display NoticeResponse
messages, even when the connection is nominally idle".
So I now added code to process Error 'N'otifications as well.
| Attachment | Content-Type | Size |
|---|---|---|
| processNotifies.patch | text/plain | 4.9 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Oliver Jowett | 2005-04-11 04:22:29 | Re: implementing asynchronous notifications |
| Previous Message | Andras Kadinger | 2005-04-11 03:34:23 | Re: implementing asynchronous notifications |