On Tue, Jan 23, 2018 at 3:32 AM, 'yz' via grpc.io <[email protected]> wrote:
> My concern is that if the client connection is closed, no matter > gracefully or not, the application layer might need to do some cleaning > according to the event, e.g., to remove authentication information from the > server. Haven't find a way to do that. > Any RPCs that were active at the time will be closed. That is a notification is good to use. If you're using the TCP connection as a session, then I'd suggest you strongly consider another option, like some simplistic caching; there are lots of things that can go wrong with using knowledge of which TCP connection and RPC is using. -- 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/CA%2B4M1oN_sustmM2r7x%3D7KZ11g_dUNJh1dQ4_bTXgVgt2qBJD0Q%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
