Re: Practical impediment to supporting multiple SSL libraries

> -----Original Message-----
> From: Stephen Frost [mailto:sfrost(at)snowman(dot)net]
> Sent: 13 April 2006 11:44
> To: Martijn van Oosterhout
> Cc: Dave Page; pgsql-hackers(at)postgresql(dot)org; Hiroshi Inoue
> Subject: Re: [HACKERS] Practical impediment to supporting
> multiple SSL libraries
>
> Instead of having it hijack the libpq connection and
> implement the wireline protocol itself, why don't we work on
> fixing the problems (such as the double-copying that libpq
> requires) in libpq to allow the driver (and others!) to use
> it in the 'orthodox' way?
>
> I would have spoken up on the ODBC list if I understood that 'hybrid'
> really meant 'just using libpq for
> connection/authentication'. I really think it's a bad idea
> to have the ODBC driver reimplement the wireline protocol
> because that protocol does change from time to time and
> someone using libpq will hopefully have fewer changes (and
> thus makes the code easier to maintain) than someone
> implementing the wireline protocol themselves (just causing
> more busy-work that, at least we saw in the past with the
> ODBC driver, may end up taking *forever* for someone to be
> able to commit the extra required time to implement).

This has been the subject of discussion for many months and the
concencus was that the most effective approach was the hybrid one which
has now been moved into CVS tip. Those involved are fully aware of the
maintenance issues of implementing the wire protocol in the driver, as
well as the difficulties using libpq entirely caused (that is how the
08.01.xxxx driver works). Changing direction again simply isn't going to
happen.

Regards, Dave