[erlang-questions] fyi: Google protocol buffers

[Torben Hoffmann]

Nice, but I must be getting old, cynical or blind to the somehow obvious
novelty in this.
Or maybe it is all of the above...

Anyway, I read through the documentation they have on this and it seems like
it is a re-invention of ASN.1 when it comes to encoding and decoding of the
messages you define the .proto files.

One can read more about ASN.1 @ http://asn1.elibel.tm.fr/tools/tutorial/

I have only used 15 minutes to read about it, but I think I can spot an
ASN.1 clone when I see one... ;-)

Or maybe a person brighter than me (there are bundles of these around) can
explain why this approach is so much better than ASN.1?!?!

Cheers,
Torben

p.s. Any intentional or unintentional harshness in this mail is directed
towards the creators of protocol buffers. Nothing but good wipes towards
Christian.

On Tue, Jul 8, 2008 at 10:01 AM, Christian S <chsu79@REDACTED> wrote:

> http://code.google.com/apis/protocolbuffers/docs/overview.html
>
> "Protocol buffers are now Google's lingua franca for data – at time of
> writing, there are 48,162 different message types defined in the
> Google code tree across 12,183 .proto files. They're used both in RPC
> systems and for persistent storage of data in a variety of storage
> systems."
>
> They're using it over XML, which I find noble (apparently XML has too
> much overhead even if you have thousands of machines, who would have
> known?), but protocol buffers it is no UBF.  :-)
> _______________________________________________
> erlang-questions mailing list
> erlang-questions@REDACTED
> http://www.erlang.org/mailman/listinfo/erlang-questions
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-questions/attachments/20080709/d2f3ad2d/attachment.htm>