X-Original-To: pgsql-hackers@postgresql.org Received: from houston.familyhealth.com.au (unknown [203.59.48.253]) by postgresql.org (Postfix) with ESMTP id 7F14047634E for ; Wed, 12 Mar 2003 20:57:35 -0500 (EST) Received: (from root@localhost) by houston.familyhealth.com.au (8.11.6/8.11.6) id h2D1vcm99182 for pgsql-hackers@postgresql.org; Thu, 13 Mar 2003 09:57:38 +0800 (WST) (envelope-from chriskl@familyhealth.com.au) Received: from mariner (mariner.internal [192.168.0.101]) by houston.familyhealth.com.au (8.11.6/8.9.3) with SMTP id h2D1vV798932; Thu, 13 Mar 2003 09:57:31 +0800 (WST) Message-ID: <094601c2e903$f10e5fe0$6500a8c0@fhp.internal> From: "Christopher Kings-Lynne" To: "Barry Lind" , "Tom Lane" Cc: References: <19041.1047322279@sss.pgh.pa.us> <3E6EEA9B.3050201@xythos.com> <27307.1047485980@sss.pgh.pa.us> Subject: Re: Roadmap for FE/BE protocol redesign Date: Thu, 13 Mar 2003 09:57:43 +0800 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1106 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-scanner: scanned by Inflex 0.1.5c - (http://www.inflex.co.za/) X-Archive-Number: 200303/514 X-Sequence-Number: 36760 > > 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