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 webpage provides documentation for various versions of `ClientContext`, ranging from version 2.7.1 to the latest version 2.63.1, with version 2.39.0 being highlighted."],["`ClientContext` is an abstract class that encapsulates client state, including executor, credentials, and transport channel, and is primarily intended for use in generated code, rather than direct user interaction."],["`ClientContext` offers methods for managing resources, such as `getBackgroundResources()`, and for retrieving configurations like credentials, the endpoint, and the executor using methods like `getCredentials()`, `getEndpoint()`, and `getExecutor()`."],["The class includes static methods `create()` to instantiate `ClientContext` based on `ClientSettings` or `StubSettings` and `newBuilder()` to create a `ClientContext.Builder`, which can throw an `IOException`."],["The class includes the feature of using `ApiTracerFactory`, which at the moment is still in Beta and not stable."]]],[]]
