Tom Lane wrote:
> I'm coming around to the idea that the cleanest solution is to require
> *all* protocol messages, in both directions, to have an initial length
> word. That is, the general message format would look like
> <message type> 1 byte
> <payload length> number of following bytes (4 bytes MSB-first)
> ... message data as needed ...
Is there any message - speaking from a standpoint of a normal user and not a
source hacker WRT postgresql - where knowing the length of the response is
either unknown or is expensive (in buffering) to find out ? This would be
the only disadvantage I can immediately see.
Sorry if I have the wrong end of the stick.
In response to
pgsql-hackers by date
|Next:||From: pgsql-bugs||Date: 2003-04-10 12:11:35|
|Subject: Bug #943: Server-Encoding from EUC_TW to UTF-8 doesn't work|
|Previous:||From: Davide Romanini||Date: 2003-04-10 09:04:37|
|Subject: Charset encoding and accents|
pgsql-interfaces by date
|Next:||From: Himmet Karaman||Date: 2003-04-10 12:44:40|
|Subject: PLEASE HELP ME about choosing entries while entering data to fields|
|Previous:||From: Matt Fitzgerald||Date: 2003-04-10 07:32:17|
|Subject: Re: Getting to learn libpqxx|