From: | Magnus Hagander <magnus(at)hagander(dot)net> |
---|---|
To: | Andrew Chernow <ac(at)esilo(dot)com> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Merlin Moncure <mmoncure(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PQinitSSL broken in some use casesf |
Date: | 2009-03-30 15:56:21 |
Message-ID: | 6DD17E57-100E-4751-B6E3-47F60A56376A@hagander.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 30 mar 2009, at 17.24, Andrew Chernow <ac(at)esilo(dot)com> wrote:
> Tom Lane wrote:
>> BTW, unless someone objects I'd like to make the name of that
>> function
>> PQinitSecurity.
>
> Agreed. Although, both PQinitSecure and PQinitSecurity are very
> general names. "Security" can mean a lot of things. Maybe the name
> should be more particular, like PQinitOpenSSL. I think its okay to
> reference the openssl project name being how this function is
> designed to work with openssl's library split.
>
+1
It's quite likely that well want to support another ssl library in the
future. At least likely enough that any api we define should take it
into consideration.
/Magnus
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Haas | 2009-03-30 16:02:20 | Re: PQinitSSL broken in some use casesf |
Previous Message | Guillaume Lelarge | 2009-03-30 15:46:27 | Re: gettext, plural form and translation |