home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!wupost!cs.utexas.edu!sun-barr!news2me.ebay.sun.com!exodus.Eng.Sun.COM!sxn
- From: sxn@eng.sun.com (Steve Nahm)
- Newsgroups: comp.protocols.nfs
- Subject: Re: XDR
- Date: 19 Aug 92 04:18:16 GMT
- Organization: Sun Microsystems Inc., Mountain View, CA
- Lines: 32
- Message-ID: <sxn.714197896@rand>
- References: <1992Aug17.064823.12057@csuvax1.csu.murdoch.edu.au>
- NNTP-Posting-Host: rand
-
- wai@csuvax1.csu.murdoch.edu.au (Julian Wai) writes:
-
- >Hi,
-
- Hi.
-
- >Can anyone explain the difference between implicit and explicit typing
- >mentioned in rfc1014? Is the example given at the end of the standard
- >explicit or implicit?
-
- "Explicit typing" is when a type field is included in the data stream. XDR
- uses implicit typing, which means that the data stream does *not* include any
- type information. Instead, both sides (the reader and writer, or the client
- and server) know in advance the type of data that's to be interpreted. ANS.1
- uses explicit typing.
-
- The example at the end is encoded in XDR, therefore it uses implicit typing.
- You interpret is by looking at the XDR description immediately preceding the
- example, and by knowing how things like enums and strings are encoded in XDR.
-
- Explicit typing can be useful, for example when you intend to store data that
- is read later by some other application. A package called "netcdf" was
- developed at UCAR which stores data in a "self-describing" format. Check the
- anonymous FTP directory pub/netcdf at unidata.ucar.edu.
-
- >Thanks in advance.
-
- You're welcome after the fact.
-
- --
- Steve Nahm sxn@sun.COM or sun!sxn
-
-