From mboxrd@z Thu Jan  1 00:00:00 1970
Message-ID: <8d4f6d07b2325d9e9ca9252497155017@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] byte order problem in aan?
From: Peter Bosch <pb@research.bell-labs.com>
In-Reply-To: <200402111619.i1BGJmJ17116@zamenhof.cs.utwente.nl>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Date: Wed, 11 Feb 2004 11:22:51 -0500
Topicbox-Message-UUID: ddfae76a-eacc-11e9-9e20-41e7f4b1d025

>> > do what aan ought to have done ...
>> > pack and unpack the values using a fixed byte order.
>>
>> yup, this need to be fixed.  i'll do it tonight...
>
> thanks. main reason I was asking, was to have a coordinated fix
> (to keep my experimental uaan in sync with sources)

i'll use network order inside the header data structure.  the reality
is that the current code is also compiler dependent.  here's my proposed
data message:

typedef struct {
	uchar		nb[4];	// Number of data bytes in this message
	uchar		msg[4];	// Message number
	uchar		acked[4];	// Number of messages acked
} Hdr;