You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current asn.1 codec maps some constructs directly to their corresponding objects, (INTEGER, SEQUENCE, etc...) and maps everything else to a tuple of (kind, tag, data).
It might be nice to use derived classes to indicate exact asn.1 types. This would also help to make the codec a round-trip one: you can feed the output of the decoder to the encoder and get back the original asn.1.
For example, have a BITSTRING class derived from bytes, have an ENUM class derived from int, etc...
With these changes we could still have efficient and easy-to-use output.
The text was updated successfully, but these errors were encountered:
The current asn.1 codec maps some constructs directly to their corresponding objects, (INTEGER, SEQUENCE, etc...) and maps everything else to a tuple of (kind, tag, data).
It might be nice to use derived classes to indicate exact asn.1 types. This would also help to make the codec a round-trip one: you can feed the output of the decoder to the encoder and get back the original asn.1.
For example, have a BITSTRING class derived from bytes, have an ENUM class derived from int, etc...
With these changes we could still have efficient and easy-to-use output.
The text was updated successfully, but these errors were encountered: