[erlang-questions] Getting support for X.692 in the asn1 application OR "If not ASN.1, then what?"
Mon May 4 08:19:46 CEST 2009
X.692 is not supported and will probably not be that in the nearest future.
Torben Hoffmann wrote:
> ECN = X.692 ;-)
> The problem with the lovely binaries in Erlang is that I have to write
> the encode/decode functions myself.
> I want to be able to specify how my PDUs look like and get the
> encode/decode for free just like with the asn1 application.
> p.s. I am not lazy, I am a mathematician!!
> On Fri, May 1, 2009 at 12:04 AM, Cameron Kerr <
> <mailto:>> wrote:
> Would ASN.1's ECN (Explicit Coding Notation) work for this?
> Not sure if that is supported by the asn1 module either... if not,
> then Erlang's binary support should be pretty useful.
> On 30/04/2009, at 8:59 PM, Torben Hoffmann wrote:
>> I am looking into finding efficient ways of dealing with legacy
>> protocols and during that I found the X.692 standard:
>> The ASN.1 compiler barfs on the ELM and EDM modules since X.692
>> is not supported by the asn1 application.
>> What are the chances of X.692 being supported by the asn1
>> A aside: no matter how fun it really is to code Erlang nothing
>> beats getting a pair of encode-decode functions for free.
>> BTW: the key need I am trying to address is the ability to
>> specify the PDUs of an arbitrarily weird protocol (mostly telecom
>> ones) and then get a codec for it. ASN.1 is not a holy grail for
>> me and other good technologies will be looked at if you suggest it.
>> Thanks in advance,
>> erlang-questions mailing list
> Cameron Kerr < <mailto:>>
> Teaching Fellow, Computer Science, University of Otago
> erlang-questions mailing list
More information about the erlang-questions