Re: Practical impediment to supporting multiple SSL libraries - Mailing list pgsql-hackers

From Greg Stark
Subject Re: Practical impediment to supporting multiple SSL libraries
Date
Msg-id 871ww0h5hf.fsf@stark.xeocode.com
Whole thread Raw
In response to Re: Practical impediment to supporting multiple SSL libraries  ("Zeugswetter Andreas DCP SD" <ZeugswetterA@spardat.at>)
Responses Re: Practical impediment to supporting multiple SSL libraries  (Greg Stark <gsstark@mit.edu>)
List pgsql-hackers
"Zeugswetter Andreas DCP SD" <ZeugswetterA@spardat.at> writes:

> > Well, the psqlODBC driver apparently ran into a number of problems with
> > libpq that resulted in them not using it for their purpose. Given libpq
> > primary purpose is to connect to PostgreSQL, it failing at that is
> > something that should be fixed.
> 
> I think you are forgetting, that e.g. a JDBC driver will not want to depend
> on an external C dll at all. It will want a native Java implementation
> (Group 4). Thus imho it is necessary to have a defined wire protocol, which
> we have.

I think you are forgetting that this is a complete nonsequitor. 

Nobody suggested eliminating the defined wire protocol. Nor was anybody even
discussing JDBC. Java folks' fetish for reimplementing everything in Java is
entirely irrelevant.

-- 
greg



pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas DCP SD"
Date:
Subject: Re: Practical impediment to supporting multiple SSL libraries
Next
From: Andreas Pflug
Date:
Subject: Re: Control File