Article View: comp.protocols.iso
Article #921Re: XOM and XDS - more info
From: Daniel Fauvarque - Sun ICNC
Date: Fri, 16 Oct 1992 00:08
Date: Fri, 16 Oct 1992 00:08
17 lines
1318 bytes
1318 bytes
|> Encode/Decode |> ------------- |> |> These merely create the relevant structures for sending/receiving ASN.1 |> data relevant to the protocol stack in use. (We use PEPSY for ISODE) |> As far as I know, the om_encode, om_decode functions are used only for transferring an XOM ASN1 encoded object between two packages in the same application with the two packages written by different suppliers (they need to use the external ASN1 representation to understand the content of the object). The real encoding shall be performed automatically by the transfer functions when you send your object to the remote. On reception the reception function decodes the received object before to allow the application to consult it.
Technical Details
Message-ID:
<lds1vvINNg6p@exodus.Eng.Sun.COM>Path:
arc1-ca.pugleaf.net!sparky!uunet!kithrup!stanford.edu!agate!usenet.ins.cwru.edu!gatech!emory!swrinde!cs.utexas.edu!sun-barr!male.EBay.Sun.COM!exodus.Eng.Sun.COM!vulcain!dfauvarqReferences:
<1992Oct14.195612.9110@walter.bellcore.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!kithrup!stanford.edu!agate!usenet.ins.cwru.edu!gatech!emory!swrinde!cs.utexas.edu!sun-barr!male.EBay.Sun.COM!exodus.Eng.Sun.COM!vulcain!dfauvarq From: dfauvarq@vulcain.France.Sun.COM (Daniel Fauvarque - Sun ICNC) Newsgroups: comp.protocols.iso Subject: Re: XOM and XDS - more info Message-ID: <lds1vvINNg6p@exodus.Eng.Sun.COM> Date: 16 Oct 92 00:08:31 GMT References: <1992Oct14.195612.9110@walter.bellcore.com> Reply-To: dfauvarq@vulcain.France.Sun.COM Organization: Sun Microsystems, Inc. Lines: 17 NNTP-Posting-Host: vulcain.france.sun.com