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 26264c25a5 Don't require NASM to build unless using the x64 decoder. 14 years ago
benchmarks Make proto2 benchmarks use ParsePartial, to make results vs upb more comparable. 14 years ago
lang_ext Added escaping for text output. 14 years ago
src Don't require NASM to build unless using the x64 decoder. 14 years ago
tests Pass the upb_fielddef* to the endmsg callback. 14 years ago
.gitignore Makefile is much improved ("make deps" works again, etc). 16 years ago
LICENSE More work on the decoder. 15 years ago
Makefile Don't require NASM to build unless using the x64 decoder. 14 years ago
README Revive Lua extension. 14 years ago
gen-deps.sh Cleanup Makefile and mv descriptor/ -> src/ 14 years ago
perf-regression-test.py Precompute bit offset and bitmask for a small perf improvement. 14 years ago
perf-tests.sh Remove upb_dstate and specialize upb_decode_fixed for perf improvement. 14 years ago

README


upb - a minimalist implementation of protocol buffers.

For API documentation, see the header files.

To build:
$ make

Other useful targets:
$ make test
$ make benchmark
$ make lua (requires lua libraries to be installed)

Issue tracking is on Google Code:
http://code.google.com/p/upb/issues/list

A manual is forthcoming, for now see wiki docs at:
https://github.com/haberman/upb/wiki

API and ABI are both subject to change! Please do not distribute as a shared
library for this reason (for now at least).

TODO
====

The issue tracker contains small-to-medium tasks that need doing; but here are
the major things that are broken or not yet implemented yet:

- serialization isn't written yet (only deserialization)

- the language extensions that exist so far (Python and Lua) are totally
incomplete/broken. They are not usable for anything yet. This will
be remedied very soon.


CONTACT
=======

Author: Joshua Haberman (jhaberman@gmail.com, haberman@google.com)
See LICENSE for copyright information.