Re: OO / fe-be protocol

As an alternative you might consider XDR (RFC 1832, RFC 1014).

http://landfield.com/rfcs/rfc1832.html
http://landfield.com/rfcs/rfc1014.html

We are using this since many years. It is quite effective. XDR is available
on a lot of platforms (on QNX too).

In short:
The data structures/unions to be transfered between different platforms must
be defined in a normal C header. This header has to be proceeded by the tool
rpcgen. This rpcgen tool generates encoding/decoding functions for these
structures. These functions can than be called in the code before send and
after receive to encode/decode message buffers.

No things like ORBs etc. are required.

Regards,
Andreas Kardos

-----Ursprüngliche Nachricht-----
Von: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
An: Chris Bitmead <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au>
Cc: <pgsql-hackers(at)postgreSQL(dot)org>
Gesendet: Freitag, 19. Mai 2000 22:50
Betreff: Re: [HACKERS] OO / fe-be protocol

> (Or we could do neither, instead inventing a brand-new protocol that's
> still Postgres-only, but that seems like it has no particular
> attraction... there's a lot of work invested in the current frontends
> and if we're going to throw it away we probably ought to adopt a
> standards-based protocol. IMHO anyway.)
>
> regards, tom lane
>