Postgres Pro
Downloads
Home   >   mailing lists

Re: [INTERFACES] Seperating interfaces from backend code - Mailing list pgsql-interfaces

From Peter T Mount
Subject Re: [INTERFACES] Seperating interfaces from backend code
Date
Msg-id Pine.LNX.4.04.9812162056210.2322-100000@maidast.retep.org.uk
Whole thread Raw
In response to Seperating interfaces from backend code  (Adam Haberlach <haberlaa@ricochet.net>)
List pgsql-interfaces
Tree view 
On Wed, 16 Dec 1998, Adam Haberlach wrote:

>     I have a (so-far) working port of libpq and libpq++ for
> BeOS, which only works with sockets over the network (since a
> server port is a long wasy off this isn't a problem.)
>     Is it possible to distribute client/interface code
> seperate from the main distribution?

The Java JDBC driver is implemented with it's own Makefile, mainly because
it doesn't refer to the rest of the source.

As for distributing the interfaces, I keep a pre-compiled binary on my
website, so there isn't a problem. This is made even easier as the driver
is platform independent.

I'm not sure, but (out of interest) has anyone ported Java to BeOS yet?

--
       Peter T Mount peter@retep.org.uk
      Main Homepage: http://www.retep.org.uk
PostgreSQL JDBC Faq: http://www.retep.org.uk/postgres
 Java PDF Generator: http://www.retep.org.uk/pdf

pgsql-interfaces by date:

Previous
From: "Thomas G. Lockhart"
Date:
Subject: Re: [INTERFACES] Seperating interfaces from backend code
Next
From: "Hiroshi Inoue"
Date:
Subject: RE: [INTERFACES] The problem between libpq and libpgtcl for WIN32