Ariel Manzur wrote:
> On Jan 5, 2008 3:13 PM, Bruce Momjian <bruce@momjian.us> wrote:
> > Ariel Manzur wrote:
> > > Hi..
> > >
> > > I need to port libpq to a platform that doesn't have a POSIX-like
> > > network API, so I was wondering if the network usage on libpq was
> > > layered somehow? I noticed that it has code for win32, so I guess
> > > there's something, but I didn't see much. Is there any documentation
> > > on how to do this?
> >
> > There is no documentation I know of about porting libpq to other
> > platforms. It normally "just works", with some adjustments for Win32,
> > as you mentioned. If you are more specific about problems you are
> > having we can help.
>
> No "problems" yet, just looking at what I need to get started.. I
> noticed that it includes other libraries like openssl.h and krb5.h, do
> any of those make their own calls to the posix network api? Also, is
> it supposed to also work with filesystem sockets too?
SSL, Kerberos are all optionally added via configure, so they aren't
required initially. Filesystem sockets is similarly controlled by
HAVE_UNIX_SOCKETS.
> I've been looking at the code and I see there's calls to send, recv,
> socket, etc directly, so I guess I'll have to isolate them myself.. It
> seems to include pthreads too, but it looks like it should be easy to
> replace.
Yes, the networking part is a requirement.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://postgres.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
