mirror of https://github.com/grpc/grpc.io.git
commit
a053f2667a
|
|
@ -56,12 +56,12 @@ Credentials can be of two types:
|
||||||
- **Call credentials**, which are attached to a call (or `ClientContext` in
|
- **Call credentials**, which are attached to a call (or `ClientContext` in
|
||||||
C++).
|
C++).
|
||||||
|
|
||||||
You can also combine these in a`CompositeChannelCredentials`, allowing you to
|
You can also combine these in a `CompositeChannelCredentials`, allowing you to
|
||||||
specify, for example, SSL details for the channel along with call credentials
|
specify, for example, SSL details for the channel along with call credentials
|
||||||
for each call made on the channel. A `CompositeChannelCredentials` associates a
|
for each call made on the channel. A `CompositeChannelCredentials` associates a
|
||||||
`ChannelCredentials` and a `CallCredentials` to create a new
|
`ChannelCredentials` and a `CallCredentials` to create a new
|
||||||
`ChannelCredentials`. The result will send the authentication data associated
|
`ChannelCredentials`. The result will send the authentication data associated
|
||||||
with the composed `CallCredentials`with every call made on the channel.
|
with the composed `CallCredentials` with every call made on the channel.
|
||||||
|
|
||||||
For example, you could create a `ChannelCredentials` from an `SslCredentials`
|
For example, you could create a `ChannelCredentials` from an `SslCredentials`
|
||||||
and an `AccessTokenCredentials`. The result when applied to a `Channel` would
|
and an `AccessTokenCredentials`. The result when applied to a `Channel` would
|
||||||
|
|
|
||||||
Loading…
Reference in New Issue