On Tue, Oct 18, 2016 at 1:39 AM, <[email protected]> wrote: > The point is the client needs a way to tell the server it's done and > doesn't care about any future responses. Both client and server then need > to clean up any resources and not log any exceptions.
It seems like what you're describing (at least on the client side) is "fire-and-forget" semantics, which we considered and decided not to make a part of gRPC <https://github.com/grpc/grpc/issues/2147>. -Nathaniel -- 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/CAEOYnASQGesEpLERy7MJkNq0rZGW_qOaX_1Y90By%3De260cgLaA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
