From: Peter Bosch <pb@research.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] byte order problem in aan?
Date: Wed, 11 Feb 2004 11:22:51 -0500 [thread overview]
Message-ID: <8d4f6d07b2325d9e9ca9252497155017@plan9.bell-labs.com> (raw)
In-Reply-To: <200402111619.i1BGJmJ17116@zamenhof.cs.utwente.nl>
>> > 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;
next prev parent reply other threads:[~2004-02-11 16:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-11 15:49 Axel Belinfante
2004-02-11 16:00 ` Charles Forsyth
2004-02-11 16:16 ` Peter Bosch
2004-02-11 16:19 ` Axel Belinfante
2004-02-11 16:22 ` Peter Bosch [this message]
2004-02-12 2:33 ` boyd, rounin
2004-02-12 13:03 ` Axel Belinfante
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8d4f6d07b2325d9e9ca9252497155017@plan9.bell-labs.com \
--to=pb@research.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).