BIRT 3.7
Written by: Michael Williams
Featured Refcardz: Top Refcardz:
  1. Scrum
  2. Apache Maven 2
  3. Essential MySQL
  4. Node.js
  5. Groovy
  1. jQuery Selectors
  2. Ajax
  3. Java
  4. Spring Config.
  5. Java Concurrency

Link Details

Link 93235 thumbnail
User 209500 avatar

By rlamarch
via google-opensource.blogspot.com
Published: Jul 08 2008 / 09:11

At Google, our mission is organizing all of the world's information. We use literally thousands of different data formats to represent networked messages between servers, index records in repositories, geospatial datasets, and more. Most of these formats are structured, not flat. This raises an important question: How do we encode it all? XML? No, that wouldn't work. Do we just write the raw bytes of our in-memory data structures to the wire? No, that's not going to work either. Instead, we developed Protocol Buffers. Protocol Buffers allow you to define simple data structures in a special definition language, then compile them to produce classes to represent those structures in the language of your choice.
  • 15
  • 1
  • 1350
  • 1

Comments

Add your comment
User 249531 avatar

Kaveh Shahbazian replied ago:

0 votes Vote down Vote up Reply

XML is ugly, bulky or everything...but widely standard. If I have to use some other format, I will do just JSON! We are suffering vendor dependency day and night with this strong hardware and stupid OS with anti virus and firewall on it (that I am and many are using) I do not want a "VENDOR DEPENDENT INTERNET"!

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.