My question was mainly around how to make sure the client network connection is cleaned up. I did end up with a simple mechanism to detect session inactivity and terminate you streaming rpcs at that point. If I get your question right, you just need to implement your notifications as a server streaming rpc per client/session.
On Fri, Jan 5, 2018 at 5:54 PM, <[email protected]> wrote: > Hi Arpit, > > Did you get this working? > > I am looking for similar scenario where I have to keep the list of client > session information on the server side. > Based on someother event, I have to determine which client shall handle > this event and send message to that specific client. > > I don't seem to find these details from Context ... any help would be great > > > On Tuesday, September 12, 2017 at 12:23:48 PM UTC-7, Arpit Baldeva wrote: >> >> Hi, >> >> After reading https://github.com/ejona86/pro >> posal/blob/a339b01be9eafffb1adc4db8c782469caed18bdc/A9- >> server-side-conn-mgt.md , I am looking for a small clarification. >> >> It looks like the connections are not considered idle if they have >> outstanding rpcs. That would mean it includes server streaming rpcs as >> well, right? A common use case for server streaming rpcs is to allow for a >> Server to Client Notification system. This means application need to do "no >> rpc from client in some duration" detection as well in this scenario and >> finish streaming rpc before grpc library can run the network layer clean up >> on it's end? >> >> Thanks. >> > -- > You received this message because you are subscribed to a topic in the > Google Groups "grpc.io" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/grpc-io/g9oittuh_6c/unsubscribe. > To unsubscribe from this group and all its topics, 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/77fd2acf-32a0-4452-86a1-ba6f97e782c4%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/77fd2acf-32a0-4452-86a1-ba6f97e782c4%40googlegroups.com?utm_medium=email&utm_source=footer> > . > > For more options, visit https://groups.google.com/d/optout. > -- 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/CAL2p%3D0mSMh2Kijb3RrBRi_Gqe_Sq4xk9MgFdHDSspPkgHBpx2g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
