Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!pmafire!mica.inel.gov!gem-hy!cdm
From: cdm@gem-hy.Berkeley.EDU (Dale Cook)
Newsgroups: comp.lang.c
Subject: Re: Binary data file compatibility across machines
Message-ID: <1990Dec20.162331.18619@inel.gov>
Date: 20 Dec 90 16:23:31 GMT
References: <9012171932.AA01165@bisco.kodak.COM> <2216@tuvie.UUCP>
Sender: news@inel.gov
Reply-To: cdm@gem-hy.Berkeley.EDU (Dale Cook)
Organization: Idaho National Engineering Laboratory, Idaho Falls, Idaho
Lines: 36

In article <2216@tuvie.UUCP>, hp@vmars.tuwien.ac.at (Peter Holzer) writes:
|> bilbo@bisco.kodak.COM (Charles Tryon) writes:
|> 
|> >I have (as I have noted here previously) been using XDR to solve
this problem.
|> >I am wondering, however, how many systems/machines subscribe to this
standard?
|> >We have various flavors of Sun's here (3.4, 4.0.1 Sun3, Sparc) as
well as an
|> >IBM RS/6000 which all know about XDR.  What other machines out there have
|> >XDR libraries?
|> 
|> On our DECstations running Ultrix (3.1 and 4.0) using sockets causes
|> lots of functions called xdr_* to be linked in. So obviously an XDR
|> library does exist. Unfortunately no manual pages do exist for these
|> functions.
|> 

We use it on our Masscomp and Cray/Unicos systems as well.  It is _very_
well documented by the Masscomp folks (Concurrent Computing).  I believe
that most, if not all, RPC implementations incorporate the XDR protocol.

--- Dale Cook     cdm@inel.gov

========== long legal disclaimer follows, press n to skip ===========
^L
Neither the United States Government or the Idaho National Engineering
Laboratory or any of their employees, makes any warranty, whatsoever,
implied, or assumes any legal liability or responsibility regarding any
information, disclosed, or represents that its use would not infringe
privately owned rights.  No specific reference constitutes or implies
endorsement, recommendation, or favoring by the United States
Government or the Idaho National Engineering Laboratory.  The views and
opinions expressed herein do not necessarily reflect those of the
United States Government or the Idaho National Engineering Laboratory,
and shall not be used for advertising or product endorsement purposes.