Hi, Wow, I forgot about replying to this. Apologies! You are right in your assumptions. By default, "is going to go to the wire" just means that data has been accepted by the gRPC stack and that gRPC will try to write the data to the socket (or whatever transport mechanism is being used). From gRPC's HTTP/2 layer perspective, it means that HTTP/2 flow control succeeded on the message and that it will be sent to the TCP layer for further processing.
Also, please note that gRPC C++ is now recommending the use of new callback API, which is much easier to use. On Saturday, April 16, 2022 at 11:13:27 PM UTC-7 karthik karra wrote: > Hi, > > *Context :* > > For the Async design, we use "Next" API with completion queue and this > blocking in nature until an event happens. > > In the description for "Next" API ( > https://grpc.github.io/grpc/cpp/classgrpc_1_1_completion_queue.html#a86d9810ced694e50f7987ac90b9f8c1a), > > its mentioned as* if "ok" is true, then it means that data is going to go > the wire*. > > so the moment ok is returned either with true or false, the "Next" API > gets unblocked. > > *My Understanding:* > > Underneath GRPC we have many layers and GRPC being the top most layer. > GRPC <-> HTTP/2 <-> Regular Network Stack (TCP <-> IP <-> Ethernet <-> > Physical Wire) > (*Please correct if any of this assumption is wrong*) > > *Doubt*: > > When the description is "Next" API says "...data going to wire" and > returning either true or false for "ok" variable, *what exactly does the > wire means ?* > *Is it after the GRPC layer or HTTP/2 layer or Physical wire itself or > something else ?* > > Any insights would be helpful. > > Thanks > > > > > -- 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/1c9dfa4b-1334-48ef-91c7-f2ab67675315n%40googlegroups.com.
