Re: PQinitSSL broken in some use casesf - Mailing list pgsql-hackers

From Robert Haas
Subject Re: PQinitSSL broken in some use casesf
Date
Msg-id 603c8f070903300902y7b7cd253v62813442dc1efde9@mail.gmail.com
Whole thread Raw
In response to Re: PQinitSSL broken in some use casesf  (Magnus Hagander <magnus@hagander.net>)
List pgsql-hackers
On Mon, Mar 30, 2009 at 11:56 AM, Magnus Hagander <magnus@hagander.net> wrote:
> On 30 mar 2009, at 17.24, Andrew Chernow <ac@esilo.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.

+1.

...Robert


pgsql-hackers by date:

Previous
From: Magnus Hagander
Date:
Subject: Re: PQinitSSL broken in some use casesf
Next
From: Heikki Linnakangas
Date:
Subject: Re: More message encoding woes