| From: | "Christopher Kings-Lynne" <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | "Barry Lind" <blind(at)xythos(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Roadmap for FE/BE protocol redesign |
| Date: | 2003-03-13 01:57:43 |
| Message-ID: | 094601c2e903$f10e5fe0$6500a8c0@fhp.internal |
| 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.
Is that something that the 'XDR' spec deals with? (Thinking back to 3rd
year networking unit)...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dave Cramer | 2003-03-13 02:09:05 | Re: Roadmap for FE/BE protocol redesign |
| Previous Message | Christopher Kings-Lynne | 2003-03-13 01:55:30 | Re: Roadmap for FE/BE protocol redesign |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Barry Lind | 2003-03-13 02:27:57 | Re: Roadmap for FE/BE protocol redesign |
| Previous Message | Tom Lane | 2003-03-12 16:19:40 | Re: Roadmap for FE/BE protocol redesign |