Encapsulates client state, including executor, credentials, and transport channel.
Unlike ClientSettings which allows users to configure the client,
ClientContext is intended to be used in generated code. Most users will not need to use it.
The objects that need to be closed in order to clean up the resources created in the process of
creating this ClientContext. This will include the closeables from the transport context.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-21 UTC."],[[["The latest version available is 2.63.1, with a comprehensive list of versions from 2.62.0 down to 2.7.1 also provided on this page."],["`ClientContext` is an abstract class that encapsulates client state, including executor, credentials, and transport channel, intended for internal use in generated code rather than direct interaction by most users."],["`ClientContext` can be instantiated using either `ClientSettings` or `StubSettings`, with static methods `create(ClientSettings settings)` and `create(StubSettings settings)` handling the instantiation processes."],["`ClientContext` provides several methods to access the client state and resources such as `getExecutor`, `getCredentials`, `getTransportChannel`, `getEndpoint`, among others, that are used in the execution of API calls."],["The ClientContext builder can be used with the `newBuilder()` method and can also utilize the current `ClientContext` by using `toBuilder()`."]]],[]]
