Eugen.Konkov@aldec.com wrote:
> server side: writeInt32( length($message)+4 ); writeString( $message );
> client side: $length= readInt32(); readString( $length -4 )
>
> that's just odd, needing to add the number of bytes the length field occupies
>
> This is simpler:
> server side: writeInt32( length($message)); writeString( $message );
> client side: $length= readInt32(); readString( $length )
>
> Will you plan to correct that in Protocol 3.1?

Agreed, no plans to change that. TCP does the same:

http://www.ysn.ru/docs/cie/Course/Section4/8.htm

+--------+--------+--------+--------+
| Source Address |
+--------+--------+--------+--------+
| Destination Address |
+--------+--------+--------+--------+
| zero | PTCL | TCP Length |
+--------+--------+--------+--------+

The TCP Length is the TCP header length plus the data length in
-----------------
octets (this is not an explicitly transmitted quantity, but is
computed), and it does not count the 12 octets of the pseudo
header.


--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs