From ff32ccdcb84e57ff7bee2c59654ec363737442c2 Mon Sep 17 00:00:00 2001 From: tjgq Date: Tue, 17 Mar 2026 14:30:12 -0700 Subject: [PATCH] Split the gRPC and non-gRPC parts of GrpcServerImpl into separate classes. This makes it possible for a followup to move GrpcCommandServerImpl into the service component, while keeping CommandServer in the logic component (with GrpcCommandServer as the interface between them). There are some improvements yet to be made around exception handling in GrpcCommandServer.Responder (see comment in GrpcCommandServerImpl.BlockingStreamObserver) but I want to do them separately, as they entail some breakage risk. PiperOrigin-RevId: 885212357 --- docs/contribute/codebase.mdx | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/contribute/codebase.mdx b/docs/contribute/codebase.mdx index 98935ab8fea17e..2a66bac46c42d3 100644 --- a/docs/contribute/codebase.mdx +++ b/docs/contribute/codebase.mdx @@ -87,8 +87,7 @@ third Ctrl-C, the client sends a SIGKILL to the server instead. The source code of the client is under `src/main/cpp` and the protocol used to communicate with the server is in `src/main/protobuf/command_server.proto` . -The main entry point of the server is `BlazeRuntime.main()` and the gRPC calls -from the client are handled by `GrpcServerImpl.run()`. +The main entry point of the server is `BlazeRuntime.main()`. ## Directory layout