We could then do things like act as a proxy service. Clients trying to connect to an external server would be redirected to this service. This service will then make a connection to actual server for each connected client and forward the RPC (of course after some kind of processing that involves some policy ).
-Jo On Wednesday, May 9, 2018 at 12:00:41 PM UTC-7, Christopher Warrington - MSFT wrote: > > On Tuesday, May 8, 2018 at 9:32:25 AM UTC-7, [email protected] wrote: > > > - For every connection, we should be able to get the events unique to > that connection in completion queue > > Pretend you had such an API. Can you share how you would make us of it and > what higher-level problem it would let you solve? > > There may be a different way to solve the same problem that doesn't need a > per-connection completion queue... > > -- > Christopher Warrington > Microsoft Corp. > -- 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/07464f97-0f5b-4ecd-8b44-5de707c0eebe%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
