The gRPC public API now provides a way for custom endpoint implementations to be provided to the library. It's called the EventEngine API, and you can read the generated API docs here <https://grpc.github.io/grpc/cpp/classgrpc__event__engine_1_1experimental_1_1_event_engine.html> (though I find the interface code itself <https://github.com/grpc/grpc/blob/123da4a866d278b898516c27fb44962f3d7bae32/include/grpc/event_engine/event_engine.h> more readable). To control the details of how bytes are sent and received, your task would be to write a complete EventEngine implementation and provide it to gRPC at runtime via the SetEventEngineFactory <https://github.com/grpc/grpc/blob/123da4a866d278b898516c27fb44962f3d7bae32/include/grpc/event_engine/event_engine.h#L481-L491> method. On Wednesday, May 10, 2023 at 7:51:57 PM UTC-7 Saigut wrote:
> I want to manage the sending and receiving of bytes under grpc myself. And > I may use a > reliable transmission protocol rather than TCP. > > From this https://groups.google.com/g/grpc-io/c/6-DyXDp2WiY/m/kdAqjknABQAJ > , I know that we can create an cutom endpoint. > > But how to achieve it? is there any document or example? > > Thank you. > -- You received this message because you are subscribed to the Google Groups "grpc.io" group. To unsubscribe from this group and stop receiving emails from it, send an email to grpc-io+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/e374c305-45e2-4c5e-af52-99347a8990cbn%40googlegroups.com.
