Re: Non-blocking communication between a frontend and a backend (pqcomm)

Hi,

On Sat, Jul 25, 2009 at 8:39 AM, Tom Lane<tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Oh, another gripe: I'll bet a nickel that this doesn't work very nicely
> under SSL.  Bytes available on the socket doesn't necessarily equate to
> decrypted payload bytes being available.  Depending on how you're using
> secure_poll, that might be okay, but it seems like a hazard waiting to
> trap unwary maintainers.

Is it only necessary to add the comment about how to use secure_poll?

There is the assumption that secure_poll must be used with secure_write/read
(e.g., in read case, pq_recvbuf instead of native recv should be called after
passing pq_wait). So, it's assumed that encrypted data are resolved in those
R/W functions and only decrypted data are located in buffer.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center