ForwardingServerBuilder
, ForwardingChannelBuilder2
, and ForwardingChannelBuilder
. Note that ForwardingChannelBuilder
is stabilized (no changes will be made to it), but immediately deprecated in favor of ForwardingChannelBuilder2
. (#10586)ForwardingChannelBuilder.delegate()
. De facto this deprecates the class itself, since all classes extending ForwardingChannelBuilder
implement the delegate()
method. See javadoc for details (#10587)LoadBalancer.acceptResolvedAddresses()
to return Status
instead of boolean
(#10636). This is part of continued work to align the LB API cross-language and API stabilizationForwardingChannelBuilder2
(#10587)ProtoUtils.metadataMarshaller()
(#10628)ManagedChannel
s now check the address types provided by the nameResolver (for the given target) with the address types supported by the channel transport and generate an error in case of mismatch. That dramatically improves the error message when an issue occursStatus.UNKNOWN
returned to the client will have Application error processing RPC
description. Previously the description was empty. This is helpful to differentiate between server errors originated in user application, gRPC library, or even those injected by a proxy. (#10643)Http2Headers.isEmpty()
. This fixes compatibility with Netty 4.1.101.Final.NettyServerBuilder.maxRstFramesPerWindow()
. This can be used to limit impact of Rapid Reset@anthonyjpratti
@fedorka
@jpd236
@mateusazis
@pkoenig10
@yannickepstein
@amirhadadi