On Tue, 3 May 2005 13:02:46 -0500"Dave Held" <dave.held@arraysg.com> wrote:
>How about an optional second connection to send keepalive
>pings?
>It could be unencrypted and non-blocking. If
authentication is needed
>on the ping port (which it doesn't seem like itwould
needto be),
>it could be very simple, like this:
>
>* client connects to main port
>* server authenticates client normally
>* server sends nonce token for keepalive authentication
>* client connects to keepalive port
>* client sends nonce token on keepalive port
>* server associates matching keepalive connection with
main connection
>* if server does not receive matching token within a small
> timeout, no keepalive support enabled for this session
Yes, this looks like good.But ;
1. Do client interfaces (ODBC,JDBC OLEDB etc) need to
be changed ?
2. If a firewall is used, ppl need to know the second
port number so mean that 2 parameters should be added to
postgres the first is timeout value and the second is port
number of the second port would be used for keepalive..
Best Regards,
Adnan DURSUN
ASRIN Bili?im Hiz.Ltd.
