Hi, could anyone help clarify this comment ? https://github.com/grpc/grpc-java/blob/master/examples/src/main/java/io/grpc/examples/manualflowcontrol/ManualFlowControlClient.java#L76 In this case does "gRPC thread" refers to the "underlying IO gRPC thread pool" (named something like grpc-nio-worker... in case of Netty at least), or the application executor thread pool (which is what appears to be the case) ?
Follow up question is if I'm understanding correctly in this example, the client will send messages to the server as long as the server says it's ready, and then only start processing incoming messages, is that right ?
So the actual flow looks something like
Outgoing:
================> (isReady = false) (isReady = true) =========================>
Incoming:
<==============================At least from my testing it doesn't look like the onReadyHandler runs concurrently with the incoming stream observer. This https://github.com/grpc/grpc-java/blob/master/examples/src/main/java/io/grpc/examples/manualflowcontrol/ManualFlowControlClient.java#L66 says they're serialized on the same thread pool but not on the same thread, or do I read this wrong ?
This is my BUILD file:
load("@rules_cc//cc:defs.bzl", "cc_binary", "cc_proto_library")
load("@rules_proto//proto:defs.bzl", "proto_library")
filegroup(
name = "srcs",
srcs = glob(["**"]),
visibility = ["//visibility:public"],
)
proto_library(
name = "login_proto",
srcs = ["login.proto"],
)
cc_proto_library(
name = "login_cc_proto",
deps = [":login_proto"],
)
cc_binary(
name = "server",
srcs = ["main.cc"],
deps = [":login_cc_proto"],
)Pretty much carbon copy from the https://github.com/bazelbuild/bazel/tree/master/third_party/protobuf/3.6.1/examples page as far as I can see
Alright, so in my situation this is the directory structure:
├── WORKSPACE
├── WORKSPACE~
├── bazel-JaCa -> /home/coldmeekly/.cache/bazel/_bazel_coldmeekly/65500f9eed0925e4b4e450cd85988252/execroot/__main__
├── bazel-bin -> /home/coldmeekly/.cache/bazel/_bazel_coldmeekly/65500f9eed0925e4b4e450cd85988252/execroot/__main__/bazel-out/k8-fastbuild/bin
├── bazel-out -> /home/coldmeekly/.cache/bazel/_bazel_coldmeekly/65500f9eed0925e4b4e450cd85988252/execroot/__main__/bazel-out
├── bazel-testlogs -> /home/coldmeekly/.cache/bazel/_bazel_coldmeekly/65500f9eed0925e4b4e450cd85988252/execroot/__main__/bazel-out/k8-fastbuild/testlogs
└── server
├── BUILD
├── BUILD~
├── login.proto
├── main.cc
└── main.cc~I'm going to try and include #include "server/login.pb.h" and see if that is what you meant by virtualised
bazel-bin directory
goawayin client side, wondering what should I do for goaway exception?
