Date: Thu, 19 May 2005 12:45:15 -0700 (PDT) From: Jon Dama <jd@ugcs.caltech.edu> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: current@freebsd.org Subject: Re: BSDcan slides uploaded Message-ID: <Pine.LNX.4.53.0505191238560.25801@heave.ugcs.caltech.edu> In-Reply-To: <19736.1116495537@critter.freebsd.dk> References: <19736.1116495537@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
I think you can be a little more informative:
ASN.1 is intended to be highly bandwidth efficient. As opposed to trying
to send lots of data (over the network) with XML which is often like a
baby trying to swallow a large watermelon whole.
phk was discussing an infrequently used interface therefore asn.1 is not
per se desirable.
Though I have to take issue with Poul's opinion that writing many text
parsers is just as secure as writing one ASN.1 decoder, but then again I
wasn't at the talk so maybe Poul has one magic text parser to solve all of
the problems.
-my two cents.
On Thu, 19 May 2005, Poul-Henning Kamp wrote:
> In message <428C5BA9.2040103@inetis.com>, Karel Miklav writes:
> >Can you please explain what you mean by:
> >
> >ASN.1 - =94This is not the format you are looking for.=94
>
> It's a bastardized starwars quote.
>
> --
> Poul-Henning Kamp | UNIX since Zilog Zeus 3.20
> phk@FreeBSD.ORG | TCP/IP since RFC 956
> FreeBSD committer | BSD since 4.3-tahoe
> Never attribute to malice what can adequately be explained by incompetenc=
e.
> _______________________________________________
> freebsd-current@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org=
"
>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.53.0505191238560.25801>