From: Skip Tavakkolian <9nut@9netics.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] asn.1 alternatives
Date: Sat, 11 Feb 2006 08:57:41 -0800 [thread overview]
Message-ID: <d3b30ef5630eb05d5f08a3a9de822c2f@9netics.com> (raw)
In-Reply-To: <397b504b58a5f6c5ff602c2f19c4463a@plan9.bell-labs.com>
i wonder if this is an entropy phenomenon. when an ABSTRACT
notation is made CONCRETE, something has to give. it is as if instead
of just translating a message in English to one in French, one sent
a polyglot along with the message.
>>>> > What are the alternatives? My pick is ASN.1, any time.
>
> Ha. I'm working on a UMTS base station (another, interesting tale
> of hard real time in Plan 9) and we're using an ASN.1 compiler that
> typically takes 30-bytes ASN.1 packed messages and decompresses
> them into 5 megabyte (yes, MEGA byte) C structs. Amazing.
next prev parent reply other threads:[~2006-02-11 16:57 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-11 0:10 [9fans] More 'Sam I am' quanstro
2006-02-11 3:01 ` jmk
2006-02-11 14:29 ` [9fans] asn.1 alternatives Charles Forsyth
2006-02-11 14:54 ` Sape Mullender
2006-02-11 16:13 ` lucio
2006-02-11 16:57 ` Skip Tavakkolian [this message]
2006-02-11 16:05 ` lucio
2006-02-11 17:52 ` Marina Brown
2006-02-11 16:28 ` Dan Cross
2006-02-11 16:53 ` Charles Forsyth
2006-02-11 22:47 ` Brantley Coile
2006-02-20 0:04 ` Harri Haataja
2006-02-11 6:04 ` ASN.1 (Was: [9fans] More 'Sam I am') lucio
2006-02-11 6:54 ` geoff
2006-02-11 8:06 ` lucio
2006-02-11 8:44 ` geoff
2006-02-11 12:10 ` lucio
2006-02-11 8:55 ` Steve Simon
2006-02-11 9:16 ` Bruce Ellis
2006-02-11 7:04 ` Skip Tavakkolian
2006-02-11 7:09 ` geoff
2006-02-11 7:53 ` lucio
2006-02-11 7:53 ` Skip Tavakkolian
2006-02-11 16:37 [9fans] asn.1 alternatives quanstro
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d3b30ef5630eb05d5f08a3a9de822c2f@9netics.com \
--to=9nut@9netics.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).