Google Git
Sign in
android / platform / external / grpc-grpc / 678ee0a45db9fad679d3cac58c0e4be1bc535de0
commit678ee0a45db9fad679d3cac58c0e4be1bc535de0[log] [tgz]
authorCraig Tiller <ctiller@google.com>Wed Jun 26 08:49:24 2024 -0700
committerCopybara-Service <copybara-worker@google.com>Wed Jun 26 08:52:22 2024 -0700
treef7c7db72e7ec36ec6d2817a1707d712c7961263d
parentc901884627ed62fb906121510b7b941314caf655 [diff]
[party] Make party a concrete type (#37015)

Move event engine context to be an arena based context, and have party host arena directly.

Now `Party` can directly inject all context necessary without needing to call out to the derived type; this makes `Party` instantiable by itself (no need to inherit from it - though we'll still want to for `CallSpine` to simplify some arena lifetime management), meaning we can start to consider eliminating the base class `Activity` and merging these types.

Closes #37015

COPYBARA_INTEGRATE_REVIEW=https://github.com/grpc/grpc/pull/37015 from ctiller:chaotic-party 7f44b37b5d5ea955a3c43ae2a950b6c87f90097c
PiperOrigin-RevId: 646963003
44 files changed
tree: f7c7db72e7ec36ec6d2817a1707d712c7961263d
  1. .bazelci/
  2. .github/
  3. bazel/
  4. cmake/
  5. doc/
  6. etc/
  7. examples/
  8. fuzztest/
  9. include/
  10. spm-core-include/
  11. spm-cpp-include/
  12. src/
  13. summerofcode/
  14. templates/
  15. test/
  16. third_party/
  17. tools/
  18. .bazelignore
  19. .bazelrc
  20. .bazelversion
  21. .clang-format
  22. .clang-tidy
  23. .dockerignore
  24. .editorconfig
  25. .git-blame-ignore-revs
  26. .gitallowed
  27. .gitattributes
  28. .gitignore
  29. .gitmodules
  30. .istanbul.yml
  31. .pylintrc
  32. .pylintrc-examples
  33. .pylintrc-tests
  34. .rspec
  35. .yapfignore
  36. .yardopts
  37. _metadata.py
  38. AUTHORS
  39. black.toml
  40. BoringSSL-Package.swift
  41. BUILD
  42. build_autogenerated.yaml
  43. build_config.rb
  44. build_handwritten.yaml
  45. BUILDING.md
  46. CMakeLists.txt
  47. CODE-OF-CONDUCT.md
  48. composer.json
  49. CONCEPTS.md
  50. config.m4
  51. config.w32
  52. CONTRIBUTING.md
  53. CONTRIBUTING_STEPS.md
  54. Gemfile
  55. GOVERNANCE.md
  56. gRPC-C++.podspec
  57. gRPC-Core.podspec
  58. gRPC-ProtoRPC.podspec
  59. gRPC-RxLibrary.podspec
  60. grpc.bzl
  61. grpc.def
  62. grpc.gemspec
  63. grpc.gyp
  64. gRPC.podspec
  65. LICENSE
  66. MAINTAINERS.md
  67. Makefile
  68. MANIFEST.md
  69. NOTICE.txt
  70. Package.swift
  71. package.xml
  72. PYTHON-MANIFEST.in
  73. Rakefile
  74. README.md
  75. requirements.bazel.txt
  76. requirements.txt
  77. SECURITY.md
  78. setup.cfg
  79. setup.py
  80. TROUBLESHOOTING.md
  81. WORKSPACE
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.

Join the chat at https://gitter.im/grpc/grpc

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/cpp directory
  • C#/.NET: NuGet packages Grpc.Net.Client, Grpc.AspNetCore.Server
  • 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/grpc-js
  • Objective-C: Add gRPC-ProtoRPC dependency 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:

LanguageSource
Shared C++ [core library]src/core
C++src/cpp
Rubysrc/ruby
Pythonsrc/python
PHPsrc/php
C# (core library based)src/csharp
Objective-Csrc/objective-c
LanguageSource repo
Javagrpc-java
Kotlingrpc-kotlin
Gogrpc-go
NodeJSgrpc-node
WebJSgrpc-web
Dartgrpc-dart
.NET (pure C# impl.)grpc-dotnet
Swiftgrpc-swift