Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 74A902E2FDF for ; Thu, 31 Jan 2008 21:56:43 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 24258-01-6 for ; Thu, 31 Jan 2008 21:56:40 -0400 (AST) Received: from momjian.us (momjian.us [70.90.9.53]) by postgresql.org (Postfix) with ESMTP id CF6842E32F2 for ; Thu, 31 Jan 2008 19:13:57 -0400 (AST) Received: (from bruce@localhost) by momjian.us (8.11.6/8.11.6) id m0VNDun18941; Thu, 31 Jan 2008 18:13:56 -0500 (EST) From: Bruce Momjian Message-Id: <200801312313.m0VNDun18941@momjian.us> Subject: Re: Lack of docs for libpq C Library In-Reply-To: <10277.1201802322@sss.pgh.pa.us> To: Tom Lane Date: Thu, 31 Jan 2008 18:13:56 -0500 (EST) CC: Peter Eisentraut , pgsql-docs@postgresql.org, Alvaro Herrera , Pavel Golub X-Mailer: ELM [version 2.4ME+ PL124 (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset="US-ASCII" X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200801/63 X-Sequence-Number: 4792 Tom Lane wrote: > Peter Eisentraut writes: > >>> Furthermore HP is hardly the authoritative reference on SSL. Can't > >>> we find an RFC or something? > >> > >> See above. > > > If anything, we should link to OpenSSL, because they implement the API we are > > referring to. I don't know what HP has to do with it. > > Yeah, I was thinking a simple pointer to www.openssl.org would be more I looked at the SSL docs and they are _minimal_: http://www.openssl.org/docs/ In fact "[STILL INCOMPLETE]" is on almost every item. > appropriate. We're not here to substitute for somebody doing their > own Google search ... The HP page is not a primary Google hit --- it took me trolling though many copies of the SSL manual pages to find it. -- Bruce Momjian http://momjian.us EnterpriseDB http://postgres.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +