Deadlines apply to the whole RPC. However, you can make an interceptor that cancels the RPC if a message hasn't been received in a time period. Without going into too much detail, there are lots of different ways to handle deadlines in the streaming case, so gRPC punts this up to the application. For the (extremely common) case of Unary calls, the deadline is the right way to make sure the call eventually ends.
On Monday, March 18, 2019 at 1:41:04 PM UTC-7, Mark Fine wrote: > > How do people manage deadlines for infinite streams? The documentation on > ClientContext set_deadline() > > > https://grpc.io/grpc/cpp/classgrpc_1_1_client_context.html#ad4e16866fee3f6ee5a10efb5be6f4da6 > > indicates that "This method should only be called before invoking the rpc" > - it doesn't seem possible to re-set the deadline throughout the lifecycle > of the connection. Are deadlines precluded from infinite streams? How do > people determine when they're infinite streams potentially get stalled? > Out-of-band detection? > > Thanks! > Mark > -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/grpc-io. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/b93eeb6d-fac1-4ed7-bb49-679b8a2c7c3b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
