It is not efficient. In the future we *might* be able to optimize this away a little, but it's always going to be strictly better to keep channels around long term.
Most applications will want to create their stubs at initialization time and destroy them at shutdown. On Thu, Jun 16, 2016, 3:12 AM Mahesh Lal <mahesh.2...@gmail.com> wrote: > Hi > > We are using an approach in which we create a gRPC client with a channel, > make a single call with it and then close the connection. This gets done > for every request that needs to be made to the systems. > > Does anyone see any issues with this? Is it efficient? What's the most > accepted practice? > > Thanks. > > -- > 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. > To view this discussion on the web visit > https://groups.google.com/d/msgid/grpc-io/CALftiMoe%2B6d_H_J%2Bcx7qoyMJZZBFV56uCDe%2BT2GpTSSct9XXaA%40mail.gmail.com > <https://groups.google.com/d/msgid/grpc-io/CALftiMoe%2B6d_H_J%2Bcx7qoyMJZZBFV56uCDe%2BT2GpTSSct9XXaA%40mail.gmail.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 grpc-io+unsubscr...@googlegroups.com. To post to this group, send email to grpc-io@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/grpc-io/CAAvp3oM9%2BJvOqjnbd7t%2B6rEsfk8rudXCDtvnF3tKYxrUuTT%3DyA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
