d4e09406c1
* [OBJC] Don't add unnecessary prefixes to service class names This is the same semantics as the Objective-C protoc. This prevents cases where you have an RPC named `FOOOpener` and a objc class prefix of `FOO` becoming `FOOFOOOpener`. * Update objective_c_generator_helpers.h Apply "sanity" check * Update objective_c_generator_helpers.h Fix up bad namespacing * Update objective_c_generator_helpers.h adding `::std::string`. Not quite sure why it's needed, but apparently it's a thing. * Update objective_c_generator_helpers.h Missing semi-colon. Hopefully caffeine will kick in at some point today... thanks tvl. * Automated change: Fix sanity tests Co-authored-by: dmaclach <dmaclach@users.noreply.github.com> |
||
|---|---|---|
| .bazelci | ||
| .github | ||
| bazel | ||
| cmake | ||
| doc | ||
| etc | ||
| examples | ||
| include | ||
| spm-core-include | ||
| spm-cpp-include | ||
| src | ||
| summerofcode | ||
| templates | ||
| test | ||
| third_party | ||
| tools | ||
| .bazelignore | ||
| .bazelrc | ||
| .clang-format | ||
| .clang-tidy | ||
| .editorconfig | ||
| .gitallowed | ||
| .gitattributes | ||
| .gitignore | ||
| .gitmodules | ||
| .istanbul.yml | ||
| .pylintrc | ||
| .pylintrc-examples | ||
| .pylintrc-tests | ||
| .rspec | ||
| .travis.yml | ||
| .yapfignore | ||
| .yardopts | ||
| AUTHORS | ||
| BUILD | ||
| BUILD.gn | ||
| BUILDING.md | ||
| CMakeLists.txt | ||
| CODE-OF-CONDUCT.md | ||
| CONCEPTS.md | ||
| CONTRIBUTING.md | ||
| GOVERNANCE.md | ||
| Gemfile | ||
| LICENSE | ||
| MAINTAINERS.md | ||
| MANIFEST.md | ||
| Makefile | ||
| NOTICE.txt | ||
| OWNERS | ||
| PYTHON-MANIFEST.in | ||
| Package.swift | ||
| README.md | ||
| Rakefile | ||
| SECURITY.md | ||
| TROUBLESHOOTING.md | ||
| WORKSPACE | ||
| _metadata.py | ||
| build_autogenerated.yaml | ||
| build_config.rb | ||
| build_handwritten.yaml | ||
| composer.json | ||
| config.m4 | ||
| config.w32 | ||
| gRPC-C++.podspec | ||
| gRPC-Core.podspec | ||
| gRPC-ProtoRPC.podspec | ||
| gRPC-RxLibrary.podspec | ||
| gRPC.podspec | ||
| grpc.bzl | ||
| grpc.def | ||
| grpc.gemspec | ||
| grpc.gyp | ||
| package.xml | ||
| requirements.bazel.txt | ||
| requirements.txt | ||
| setup.cfg | ||
| setup.py | ||
README.md
gRPC - An RPC library and framework
gRPC is a modern, open source, high-performance remote procedure call (RPC) framework that can run anywhere. gRPC enables client and server applications to communicate transparently, and simplifies the building of connected systems.
| Homepage: | grpc.io |
| Mailing List: | grpc-io@googlegroups.com |
To start using gRPC
To maximize usability, gRPC supports the standard method for adding dependencies to a user's chosen language (if there is one). In most languages, the gRPC runtime comes as a package available in a user's language package manager.
For instructions on how to use the language-specific gRPC runtime for a project, please refer to these documents
- C++: follow the instructions under the
src/cppdirectory - C#: NuGet package
Grpc - Dart: pub package
grpc - Go:
go get google.golang.org/grpc - Java: Use JARs from Maven Central Repository
- Kotlin: Use JARs from Maven Central Repository
- Node:
npm install grpc - Objective-C: Add
gRPC-ProtoRPCdependency to podspec - PHP:
pecl install grpc - Python:
pip install grpcio - Ruby:
gem install grpc - WebJS: follow the grpc-web instructions
Per-language quickstart guides and tutorials can be found in the documentation section on the grpc.io website. Code examples are available in the examples directory.
Precompiled bleeding-edge package builds of gRPC master branch's HEAD are uploaded daily to packages.grpc.io.
To start developing gRPC
Contributions are welcome!
Please read How to contribute which will guide you through the entire workflow of how to build the source code, how to run the tests, and how to contribute changes to the gRPC codebase. The "How to contribute" document also contains info on how the contribution process works and contains best practices for creating contributions.
Troubleshooting
Sometimes things go wrong. Please check out the Troubleshooting guide if you are experiencing issues with gRPC.
Performance
See the Performance dashboard for performance numbers of master branch daily builds.
Concepts
See gRPC Concepts
About This Repository
This repository contains source code for gRPC libraries implemented in multiple languages written on top of a shared C core library src/core.
Libraries in different languages may be in various states of development. We are seeking contributions for all of these libraries:
| Language | Source |
|---|---|
| Shared C [core library] | src/core |
| C++ | src/cpp |
| Ruby | src/ruby |
| Python | src/python |
| PHP | src/php |
| C# (core library based) | src/csharp |
| Objective-C | src/objective-c |
| Language | Source repo |
|---|---|
| Java | grpc-java |
| Kotlin | grpc-kotlin |
| Go | grpc-go |
| NodeJS | grpc-node |
| WebJS | grpc-web |
| Dart | grpc-dart |
| .NET (pure C# impl.) | grpc-dotnet |