From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on polar.synack.me
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,FREEMAIL_FROM
	autolearn=ham autolearn_force=no version=3.4.4
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: 103376,40c8d1d2d927ffd9
X-Google-Attributes: gid103376,public
X-Google-ArrivalTime: 2004-02-20 21:34:38 PST
Path: 
 archiver1.google.com!news2.google.com!news.maxwell.syr.edu!wn54feed!worldnet.att.net!attbi_s51.POSTED!not-for-mail
From: "Steve" <nospam_steved94@comcast.net>
Newsgroups: comp.lang.ada
References: <9fb7e8e1.0402190429.49b37b16@posting.google.com>
Subject: Re: Interoperability: differing storage units and/or endianess
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
Message-ID: <M5CZb.93323$uV3.558411@attbi_s51>
NNTP-Posting-Host: 24.20.111.157
X-Complaints-To: abuse@comcast.net
X-Trace: attbi_s51 1077341676 24.20.111.157 (Sat, 21 Feb 2004 05:34:36 GMT)
NNTP-Posting-Date: Sat, 21 Feb 2004 05:34:36 GMT
Organization: Comcast Online
Date: Sat, 21 Feb 2004 05:34:36 GMT
Xref: archiver1.google.com comp.lang.ada:5704
Date: 2004-02-21T05:34:36+00:00
List-Id: <comp.lang.ada>

Check out:
  http://www.ietf.org/rfc/rfc1832.txt
For a description of XDR.
It is close to what we use for specifying data in our distributed
application.

Steve
(The Duck)


"Bibb Latting" <bibb.latting@cox.net> wrote in message
news:9fb7e8e1.0402190429.49b37b16@posting.google.com...
> Hi, I am working on a distributed application where the processors
> have differing storage unit sizes and/or endianess.  My problem is how
> to handle the specification of memory contents and the delivery of
> data to applications with minimal variation between implementations.
> I'd like to know what solutions have worked well for others.