From: Christopher Kings-Lynne <chriskl@familyhealth.com.au>
To: Barry Lind <blind@xythos.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
Date: Thu, 13 Mar 2003 09:57:43 +0800
Message-ID: <094601c2e903$f10e5fe0$6500a8c0@fhp.internal> (raw)
References: <19041.1047322279@sss.pgh.pa.us>
<3E6EEA9B.3050201@xythos.com>
<27307.1047485980@sss.pgh.pa.us>
> > One addition I would personally like to see (it comes up in my apps
> > code) is the ability to detect wheather the server is big endian or
> > little endian. When using binary cursors this is necessary in order to
> > read int data.
>
> Actually, my hope is to eliminate that business entirely by
> standardizing the on-the-wire representation for binary data; note the
> reference to send/receive routines in the original message. For integer
> data this is simple enough: network byte order will be it. I'm not sure
> yet what to do about float data.
Is that something that the 'XDR' spec deals with? (Thinking back to 3rd
year networking unit)...
Chris
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-interfaces@postgresql.org
Cc: chriskl@familyhealth.com.au, blind@xythos.com, tgl@sss.pgh.pa.us, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
In-Reply-To: <094601c2e903$f10e5fe0$6500a8c0@fhp.internal>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox