On Tue, Apr 17, 2018 at 11:31 AM, Christopher Schechter < chrissc...@gmail.com> wrote:
> I think another part of the confusion for me was that I wasn't expecting > the Server's executor thread pool to be in charge of both handling and > cancelling the RPC's. In my test, I had a fixed thread pool with 5 threads, > and sometimes would start up 5 streams to clients. Then, if a client > disconnected, the server wouldn't cancel it because it would have no > executor threads available to do so. > So to be clear, the RPC had been cancelled and the server-side library was aware of the cancellation. It was just an API thing in getting the notification to your service. -- 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 post to this group, send email to grpc-io@googlegroups.com. 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/CA%2B4M1oOFeEU84h_xiDw2L%3DM43-Pt3w5U-N4n2%2BMgCT0S2eJ5eg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
