> -----Original Message-----
> From: Stephen Frost [mailto:sfrost@snowman.net]
> Sent: 13 April 2006 11:44
> To: Martijn van Oosterhout
> Cc: Dave Page; pgsql-hackers@postgresql.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

---------------------------(end of broadcast)---------------------------
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql.org so that your
message can get through to the mailing list cleanly

* Dave Page (dpage@vale-housing.co.uk) wrote:
> 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.

There was barely any discussion at all about this... I do follow the
lists involved even though I didn't respond to the question regarding
this (either time it was asked) because I didn't understand that
'hybrid' meant 'only using libpq for the connection'. I'm curious how
many others of those being asked understood this... I think the fact
that you had to ask twice to get any response at all is a good
indication.

Does the latest verion in CVS support V3 of the wireline protocol? If I
recall correctly, the version it was based on still only supported V2...

What does the wireline protocol implementation in the ODBC driver do
that it can't get through libpq? I can certainly understand the
double-copying issue (I complained about that myself when first starting
to use libpq) but I think that could be fixed without that much
difficulty. Were there other things?

Thanks,

Stephen

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFEPjw0rzgMPqB3kigRAjEvAKCMfaczU1Mo87SdqDDBqn 95eRpNRgCgj+c1
HaqLpAvu9324UzXM2+ggffI=
=8+Mt
-----END PGP SIGNATURE-----