Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

asn.1 codec could derive from list for SEQUENCE, SET, etc... #63

Open
samrushing opened this issue Jul 29, 2014 · 0 comments
Open

asn.1 codec could derive from list for SEQUENCE, SET, etc... #63

samrushing opened this issue Jul 29, 2014 · 0 comments

Comments

@samrushing
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant