• LingBin's avatar
    Fix typo in bvar_c++.md · f4a6c92a
    LingBin authored
    There are two method to expose a bvar, one is `expose`, the other is `expose_as`
    f4a6c92a
Name
Last commit
Last update
.github Add newlines to bug/feature templates
bazel chore: update google_protobuf
cmake Fix cmake build issue when use this project as a submodule. (#428)
docs Fix typo in bvar_c++.md
example Fix CMakeLists.txt of example/auto_concurrency_limiter
java Add empty folder of python and java
python Add empty folder of python and java
src Merge pull request #738 from zyearn/add_docs_cluster_recover
test add docs for cluster recover & fix parameter unit
tools Update .bazelrc
.bazelrc Update .bazelrc
.gitignore health_check_using_rpc: add single server
.travis.yml travis: use MesaLink the 0.8.0 release
BUILD Move BinaryPrinter into separate files and make it more generic
CMakeLists.txt use cpack to generate deb package
CODE_OF_CONDUCT.md Create CODE_OF_CONDUCT.md
CONTRIBUTING.md fix travis-ci link after transfering to apache
Disclaimer add Disclaimer file
Dockerfile add docker
LICENSE Patch svn r35206 & fix compilation of tools
Makefile Makefile: fix for high version protobuf
NOTICE change NOTICE.txt to NOTICE
README.md fix travis-ci link after transfering to apache
README_cn.md fix travis-ci link after transfering to apache
WORKSPACE travis-ci support bazel build
build_in_travis_ci.sh travis: build and test the MesaLink TLS backend
config.h.in make config.h.in consistent with config_brpc.sh
config_brpc.sh find bin from --libs first
glog.BUILD bazel build support glog
leveldb.BUILD chore: fix undefined reference to butil::ReadCommandLine when to build with bazel

中文版

Build Status

brpc

An industrial-grade RPC framework used throughout Baidu, with 1,000,000+ instances(not counting clients) and thousands kinds of services, called "baidu-rpc" inside Baidu. Only C++ implementation is opensourced right now.

You can use it to:

Try it!

Contribute code

Please refer to here.

Feedback

Please report bugs, concerns, suggestions by issues, or join QQ-group 498837325 to discuss problems around source code.