<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Ron, <br>
</p>
<p>I see that originally when you had introduce ASN1 to our library,
you defined the classes ASN1WrapperConstructedType and
ASN1ExplicitContextValue. I tried to implement decode and encode
to ASN1WrapperConstructedType, but only partially. I used your
ASN1ExplicitContextValue but have not completed it. Now I have the
need to implement, as I attempt to switch the PromisesRemote to
using ASN1 encoding, rather than STON.<br>
</p>
<p>In looking at Object>>#asn1Tag we construct a tag with <br>
</p>
<blockquote>
<p>Object>>#asn1Tag<br>
<br>
^ (ASN1MappedSequenceType new asn1Tag "48"<br>
bitOr: 2r11000000) "Application"<br>
bitOr: 2r00100000 "Constructed"</p>
</blockquote>
<p>So we are an application class and constructed. In
ASN1OutputStream>>#typeForTag: tag, the tag is broken down
into the numericTag, the tagClass (application) and whether it is
constructed. This is called from decode: anObject with the call:</p>
<blockquote>
<p>^ self encode: anObject with Type: (self typeForTag: anObject
asn1Tag)</p>
</blockquote>
<p>So Object>>#asn1Tag is called. So with a ASN1
non-registered object, we end up with a
ASN1WrapperConstructedType.</p>
<p>I am totally unsure about how the ASN1ExplicitContextValue should
be used with the ASN1WrapperConstructedType, nor how it builds the
context from the ivars of the provided anonymous object.</p>
<p>My related concern is whether all of the crypto objects with ASN1
definitions ought to be of the application tagClass.</p>
<p>Any guidance you could provide me for this would be very welcome!
If it is not too far back in history! Heh!</p>
<p>Thanks!<br>
</p>
<pre class="moz-signature" cols="72">--
Have a good one; keep it, light.
Kindly,
rabbit
. .. … ‘…^,^
Sent from Callisto House :: decentralized mobile homeless solutions</pre>
</body>
</html>