Could you elaborate your suggestion? I cannot see why it's useful. Usually streaming request reactor needs some state to handle writing a series of messages to the peer.
On Thursday, March 3, 2022 at 10:02:30 AM UTC-8 Brent Edwards wrote: > This is for a service with callback processing enabled i.e. service > derived from CallbackService > > On Friday, 4 March 2022 at 07:00:48 UTC+13 Brent Edwards wrote: > >> For a unary server request you can use a default reactor. >> e.g. >> grpc::ServerUnaryReactor* reactor = context->DefaultReactor(); >> >> >> If there such an "Default" reactor for a server streaming request >> e.g. >> grpc::ServerWriteReactor<GetTracksResponse>* reactor = >> context->DefaultWriteReactor<GetTracksResponse>() >> > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/75f5b460-64ca-4585-82cf-745e1dd427f8n%40googlegroups.com.
