If done at the application level (like I do it right now due to no other options), I lose every benefit of the channels like rediscovery in case the endpoint changes (which can and will happen). Instead it will try to reconnect to the old endpoint, waiting for it to return, which will not happen. That’s why I hoped to use the existing core features of gRPCLB.
The only service with fixed port is my main service which right now works as nameservice and manages my modules. -- 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/808288e9-3192-4f7b-b932-ad68af9fb70d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
