- Original Message -
From: Gerhard Wesp [EMAIL PROTECTED]
To: FlightGear developers discussions [EMAIL PROTECTED]
Sent: Thursday, November 13, 2003 9:29 AM
Subject: Re: [Flightgear-devel] Multiplayer RFC -- wire protocol
spec --preliminary
Unless there are objections, byte order
Unless there are objections, byte order is little endian, and floats
are intel FPU standard (ok -- i'm making it easy on the PCs that will
likely be used to run display clients :)
Is there any specific reason not to use human readable messages (i.e.,
ASCII)?
It's a waste of bandwidth.
John Barrett wrote:
Here is a quick and dirty 1st cut at a wire protocol definition, and some
requirements for the message handling classes that will implement the
protocol
Unless there are objections, byte order is little endian, and floats are intel FPU standard (ok -- i'm making it easy on the
Here is a quick and dirty 1st cut at a wire protocol definition, and some
requirements for the message handling classes that will implement the
protocolPreliminary FlightGear Server (FGS) wire protocol specification
0xFFEscape prefix for 0xF? bytes in the data
next byte is inverted,
