BSDcan slides uploaded
Jon Dama
jd at ugcs.caltech.edu
Thu May 19 12:45:19 PDT 2005
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 at 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 at 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 at freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe at freebsd.org=
"
>
More information about the freebsd-current
mailing list