Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2] (may be
	forged)) by hub.org (8.9.3/8.9.3) with ESMTP id LAA24896
	for <pgsql-interfaces@hub.org>; Sat, 24 Jul 1999 11:27:53 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA01527;
	Sat, 24 Jul 1999 11:27:16 -0400 (EDT)
To: "Stephen Martin Trans-Euro I.T Ltd" <stephen@sealteam.demon.co.uk>
cc: "pg-interfaces" <pgsql-interfaces@hub.org>
Subject: Re: [INTERFACES] More VB 
In-reply-to: Your message of Sat, 24 Jul 1999 03:48:02 +0100
	<016501bed57e$f376d740$bbb4989e@station1.Marketrends.net>
Date: Sat, 24 Jul 1999 11:27:16 -0400
Message-ID: <1525.932830036@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Stephen Martin Trans-Euro I.T Ltd" <stephen@sealteam.demon.co.uk> writes:
> whilst it seems driving libpq.dll from VB might be a difficult
> enterprise..  is it still not possible to just connect a socket to
> port 5432 of where ever and start communicating with postgres through
> a socket?  TCP or UDP?

Sure, if you can cope with binary-oriented data structures being
returned to you by the server.  (The actual data is text, as long as you
don't use BINARY CURSORs, but it's wrapped in header and count fields
that are not.)  libpq isn't doing anything that's particularly magic.
See the "Frontend/Backend Protocol" chapter of the Developer's Guide for
all the gory details of the client-to-server protocol.

			regards, tom lane