commit | 41a1d4932033bcf73dee7fc45a973a96e4ef07c0 | [log] [tgz] |
---|---|---|
author | Mao <littlecvr@gmail.com> | Wed Nov 16 11:16:07 2022 +0800 |
committer | GitHub <noreply@github.com> | Wed Nov 16 11:16:07 2022 +0800 |
tree | a87c782d03d7e4edad1fe04773ea242eb2559aae | |
parent | 3be177223e5f52932602401bd6b50464ab9d8fd3 [diff] |
[BinderTransport] Fix BinderTransport server race conditions (#31654) * Set `connected_` to true before `SendSetupTransport()` A race happens when the server has already sent setup transport to the client when it's actually not ready. So move `connected_ = true` before `SendSetupTransport()`. However, this may cause another race that `wire_writer_` being used when it's actually not being constructed yet. So add another Notification for others to wait for it to be ready. Note: simply moving `SendSetupTransport()` into the mutex section could potentially cause a deadlock since it's possible that `ProcessTransaction()` being called on the same call chain. This solution is considered a workaround before we figure out a better workable solution. It's not perfect as if the first request sends, e.g., 64K of data, we'll try to send an ACK and the system will still deadlock. Furthermore, this solution makes threads waiting (although the time frame should be very short). * Store `accept_stream_fn` call count and call it later when possible We might be signaled to call `accept_stream_fn` before it has been set. We should memorize this case and call it later once it has been set, or the stream will never be accepted. * Add comments and polish the change
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.
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
src/cpp
directoryGrpc
grpc
go get google.golang.org/grpc
npm install grpc
gRPC-ProtoRPC
dependency to podspecpecl install grpc
pip install grpcio
gem install grpc
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.
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.
Sometimes things go wrong. Please check out the Troubleshooting guide if you are experiencing issues with gRPC.
See the Performance dashboard for performance numbers of master branch daily builds.
See gRPC Concepts
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 |
Swift | grpc-swift |