grpc
/
grpc-java
mirror of https://github.com/grpc/grpc-java.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

core: Internal is not necessary for LoadBalancers 

With the advent of LoadBalancer2 (now just LoadBalancer) the need to use
internal APIs was removed; there's now first-class APIs exposed for
LoadBalancer use.

The old LoadBalancer API interacted with io.grpc.internal.ClientTransport
directly.
This commit is contained in:
Eric Anderson 2018-03-08 12:54:35 -08:00
parent c7e15356d3
commit c59ddc52a1
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
core/src/main/java/io/grpc/Internal.java
View File

@ -23,13 +23,12 @@ import java.lang.annotation.RetentionPolicy;
import java.lang.annotation.Target;
/**
* Annotates a program element (class, method, package etc) which is internal to gRPC, not part of
* Annotates a program element (class, method, package, etc) which is internal to gRPC, not part of
* the public API, and should not be used by users of gRPC.
*
* <p>However, if you want to implement a custom {@link LoadBalancer}, an alternative transport, or
* anything else that will be wired into gRPC library, you may use the internal parts. Please
* consult the gRPC team first, because internal APIs don't have the same API stability guarantee as
* the public APIs do.
* <p>However, if you want to implement an alternative transport you may use the internal parts.
* Please consult the gRPC team first, because internal APIs don't have the same API stability
* guarantee as the public APIs do.
*
* <p>Note: This annotation is intended only for gRPC library code. Users should not attach this
* annotation to their own code.