Protocol Buffers - Google's data interchange format (grpc依赖) https://developers.google.com/protocol-buffers/
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Joshua Haberman 4b47002198 Update Python C extension for new upb_array API. 15 years ago
benchmarks Fixes for more discerning compilers. 15 years ago
descriptor Small bugfix: enums are int32, not uint32. 15 years ago
lang_ext/python Update Python C extension for new upb_array API. 15 years ago
src Change upb_msg to work with messages that have 0 fields. 15 years ago
tests Tests use valgrind, chdir in test. 15 years ago
tools Small bugfix: enums are int32, not uint32. 15 years ago
.gitignore
LICENSE
Makefile Tests use valgrind, chdir in test. 15 years ago
README
TODO Small C++ header fixes. 15 years ago
gen-deps.sh Add refcounting and thread-safety to message definitions. 16 years ago
perf-regression-test.py Small fix to regression script. 16 years ago
perf-tests.sh Refactoring: unify upb_msg. 16 years ago

README


upb - a minimalist implementation of protocol buffers.

- For API documentation, see the header files.
- To build type "make".


ROADMAP OF THE SOURCE
=====================

benchmark/
Benchmarks of upb and other protocol buffer implementations.
descriptor/
Files that describe the format of Protocol Buffer "descriptors", which are
protocol buffers that describe the format of other protocol buffers. These
are used extensively inside upb.
labs/
Code that is not part of upb, but contains efficiency-related experiments
about alternate ways of implementing things. When possible, these are
benchmarked by the tests in benchmark/. We also test these with the tests
in tests/, to ensure that the alternate implementations are actually correct.
src/
The core source directory. builds into src/libupb.a.
tests/
Unit tests.
tools/
Command-line tools like the upb compiler.


CONTACT
=======

Author: Joshua Haberman (joshua@reverberate.org, haberman@google.com)
See LICENSE for copyright information.