From: | Sean Chittenden <sean(at)chittenden(dot)org> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Barry Lind <blind(at)xythos(dot)com>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Roadmap for FE/BE protocol redesign |
Date: | 2003-03-13 07:04:35 |
Message-ID: | 20030313070435.GC79234@perrin.int.nxad.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-interfaces |
> > 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.
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
--
Sean Chittenden
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2003-03-13 07:33:27 | Re: Roadmap for FE/BE protocol redesign |
Previous Message | Hannu Krosing | 2003-03-13 06:54:24 | Re: Roadmap for FE/BE protocol redesign |
From | Date | Subject | |
---|---|---|---|
Next Message | Mike Mascari | 2003-03-13 07:33:27 | Re: Roadmap for FE/BE protocol redesign |
Previous Message | Hannu Krosing | 2003-03-13 06:46:13 | Re: Roadmap for FE/BE protocol redesign |