protobuf

Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/

Joshua Haberman e6fa3f9d86 Changed schema for JSON test to be defined in a .proto file. (#54 ) * Changed schema for JSON test to be defined in a .proto file. Before we had lots of code to build these schemas manually, but this was verbose and made it difficult to add to the schema easily. Now we can just write a .proto file and adding fields is easy. To avoid making the tests depend on upbc (and thus Lua) we check in the generated schema. * Made protobuf-compiler a dependency of "make genfiles." * For genfiles download recent protoc that can handle proto3. * Only use new protoc for genfiles.		9 years ago
..
googlepb	Brought into compliance with Google open-source policies.	10 years ago
linux	Brought into compliance with Google open-source policies.	10 years ago
lua	Changed schema for JSON test to be defined in a .proto file. (#54 )	9 years ago
python	Brought into compliance with Google open-source policies.	10 years ago
ruby	Brought into compliance with Google open-source policies.	10 years ago
stdc	Brought into compliance with Google open-source policies.	10 years ago
stdc++	Brought into compliance with Google open-source policies.	10 years ago
README	Sync to internal Google development.	11 years ago

README

This directory contains code that interfaces upb with external C/C++
libraries.  For example:

 * upb/bindings/{stdc,stdc++}
     interfaces between upb and the standard libraries of C and C++ (like C's
     FILE/stdio, C++'s string/iostream, etc.)

 * upb/bindings/googlepb
     interfaces between upb and the "protobuf" library distributed by Google.

 * upb/bindings/lua:
     a Lua extension that exposes upb to Lua programs via the Lua C API.

 * upb/bindings/linux:
     code and build system for building upb as a Linux kernel module.

The two key characteristics that decide whether code belongs in upb/bindings/
are:

 * Does the code's public API refer to types from another library?
   If so it belongs in upb/bindings/.  But this doesn't include code that just
   happens to use another library internally, as an implementation detail.

 * Would this code be useful to someone who is not using this external library
   in some other way?  If so, the code probably doesn't belong in upb/bindings/.