When you can, use ManagedChannelBuilder. It will auto-choose which transport, so Netty vs OkHttp, and has a stable API. We provide more advanced options in NettyChannelBuilder but it isn't a stable API. You should be able to use both TLS and plaintext with ManagedChannelBuilder.
On Tue, May 30, 2017 at 6:19 PM, <[email protected]> wrote: > Some education please on the NettyChannelBuilder vs > ManagedChannelBuilder. Code I inherited used ManagedChannelBuilder for > grpc (non-TLS) and NettyChannelBuilder for grpcs (TLS). So > NettyChannelBuilder is a subclass of ManagedChannelBuilder with more > options. Is there any reason to not just use both for grpc and grpcs ? I > think in both cases we'll want to set the keepalive option > Thanks! > > On Tuesday, May 30, 2017 at 8:58:56 PM UTC-4, [email protected] wrote: >> >> I Just noticed that NettyChannelBuilder has a keep alive option. >> >> On Tuesday, May 30, 2017 at 8:21:32 PM UTC-4, [email protected] wrote: >>> >>> Thanks that's really great information. How about Java ? Does Java do >>> this too ? >>> >>> On Tuesday, May 30, 2017 at 8:01:37 PM UTC-4, Michael Lumish wrote: >>>> >>>> For the Node client, I think you can enable keepalive HTTP2 pings using >>>> the channel argument "grpc.keepalive_time_ms" as defined at >>>> https://github.com/grpc/grpc/blob/master/include/grpc/imp >>>> l/codegen/grpc_types.h#L230 >>>> <https://www.google.com/url?q=https%3A%2F%2Fgithub.com%2Fgrpc%2Fgrpc%2Fblob%2Fmaster%2Finclude%2Fgrpc%2Fimpl%2Fcodegen%2Fgrpc_types.h%23L230&sa=D&sntz=1&usg=AFQjCNGk3KcO9EpwYHnZBq8vAxd5HlZv3w>. >>>> This argument is passed in the options object, which is the third argument >>>> to the Client constructor. >>>> >>>> On Tue, May 30, 2017 at 4:41 PM <[email protected]> wrote: >>>> >>>>> Currently Node client is looking to fix this doing a heartbeat at the >>>>> application level. Sending NOP messages This seem like something >>>>> grpc/http2 should handle. Load balancers are very common. >>>>> Don't this is off the bat a good way to fix this if it is even an >>>>> issue for Java >>>>> >>>>> -- >>>>> 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/3cc62500-4979-4c04 >>>>> -8f21-573ac4ae2cb2%40googlegroups.com >>>>> <https://groups.google.com/d/msgid/grpc-io/3cc62500-4979-4c04-8f21-573ac4ae2cb2%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/96431849-ba64-4b63-94d1-d658f87401ac%40googlegroups.com > <https://groups.google.com/d/msgid/grpc-io/96431849-ba64-4b63-94d1-d658f87401ac%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/CA%2B4M1oNnPVN5LcGnCjerKwkyiwPwj8Xk2H0ovMkJVVL98rtkWw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
smime.p7s
Description: S/MIME Cryptographic Signature
