Date: Wed, 12 Mar 2003 23:04:35 -0800
From: Sean Chittenden <sean@chittenden.org>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Barry Lind <blind@xythos.com>, pgsql-hackers@postgresql.org
Subject: Re: Roadmap for FE/BE protocol redesign
Message-ID: <20030313070435.GC79234@perrin.int.nxad.com>
References: <19041.1047322279@sss.pgh.pa.us> <3E6EEA9B.3050201@xythos.com>
	<27307.1047485980@sss.pgh.pa.us>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="ARHwKispuqSRPZ/2"
Content-Disposition: inline
In-Reply-To: <27307.1047485980@sss.pgh.pa.us>
User-Agent: Mutt/1.4i

--ARHwKispuqSRPZ/2
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

> > 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.
>=20
> 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.

When were talking sending data across the wire, are we talking about a
format that would let the server use sendfile() for sending the data
to the client? Having a database that can send data to the client
efficiently would be a nice change of pace given most databases since
RDBMSs are notoriously slow (slower than NFS) at sending files to
clients.  -sc

--=20
Sean Chittenden

--ARHwKispuqSRPZ/2
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Comment: Sean Chittenden <sean@chittenden.org>

iD8DBQE+cC2C3ZnjH7yEs0ERAiwBAKCBFn5f4Ghkvi+1OWKD9ssqavUHMACfTs9F
+pIpAUi99sXqcL7N5OJbM9k=
=aVjp
-----END PGP SIGNATURE-----

--ARHwKispuqSRPZ/2--