🚀 go-pugleaf

In article <1992Oct14.195612.9110@walter.bellcore.com>, tain@wrench.bae.bellcore.com (Tai Nguyen) writes:
|> In article <1992Oct13.020901.3410@mel.dit.csiro.au>, brian@mel.dit.csiro.au (Brian May) writes:
|> 
|>   ... Stuff deleted 
|> 
|> |> 
|> |> OIDs and Class Tables
|> |> ---------------------
|> |> 
|> |> XOM holds a _static_ class table containing all the OIDs it knows about.
|> |> If you want to dynamically use/create a new object, it'll have to be 
|> |> re-compiled into XOM's class tables.
|> |> 
|> |> Class table structure is left up to the implementor.
|> |> 
|> |> 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)
|> |> 

clarification:

These merely create the relevant structures, encoders and decoders
for sending/receiving ASN.1 data relevant to the protocol stack in use.
(We use PEPSY for ISODE)


|> it and its peer can use different stack. Thus, the encoding must be based on
|> ASN.1 syntax understood by both sides.

It is.

regards,

brian
--
| Brian.May@mel.dit.csiro.au |           Open Systems Program           |
| CSIRO/DIT, 723 Swanston st | TEL +61 3 282 2613 -- FAX +61 3 282 2600 |
|Carlton, VIC 3053, Australia|          Experimental Scientist          |