On Sat, 24 Aug 1996, Arnoud Galactus Engelfriet wrote:
> In article <a4oHysuB8gKB091yn@biddeford.com>,
> jond@biddeford.com (Jon Duckworth) wrote:
> > The folder base is actually documented in Simple Offline USENET Packet
> > Specification 1.2 (linked to from <URL:http://www.vex.net/yarn/>) as
>
> Yarn folders are big-endian, but SOUP packets of type "b" and "B"
> are LITTLE-endian.
Nope; SOUP specification 1.2 specifically says that types 'b' and 'B' are
big-endian (high-byte first, low-byte last):
[snip!]
The 'b' (binary mail) and 'B' (binary news) formats are identical. The
contents of each message must conform to RFC-822/1036 and may contain
content information compatible with RFC-1341 (MIME). The only
difference between the messages of these formats and the preceding
formats is that no assumption is made about line lengths, and any of
the 256 values for a byte may be used in any position. Each message is
preceded by a 4-byte value which indicates the length of the message
in bytes, stored in big-endian order (i.e. high byte first, low byte
last). The difference between 'b' and 'B' is a semantic one: message
files of type 'b' are expected to contain mail messages, and message
files of type 'B' are expected to contain news messages. Thus, reader
software can make a distinction between the two if it desires.
[snip]
Now that I think about it, maybe Yarn folders are little-endian (low-byte
first, high-byte last), but SOUP types 'b' and 'B' are definatly big-endian.
>
> Galactus
>
Jon
- --
Jon Duckworth -- jond@biddeford.com -- http://www.biddeford.com/~jond/
PGP Public Key: 1024/E06DD431 on http://www.pgp.net/pgp/
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
iQCVAwUBMh9pLu7yj4bgbdQxAQHRBgP/acr0Je2A0Bz3vF2x9wQRX3njp8uZRt9s
P7JuDrRc4mDwoawnX2kbDqVaVlWfm7jlJErmZRCN+1wQ0DYYlIi+YU0N3XjhgwCO
SwUVJomCMjaUDYs0/NhS7varepT24//FyrXLmyJgCdYqKy3yU5YOPG/FJRg0YcvH
occeG2xlyRQ=
=6KYY
-----END PGP SIGNATURE-----