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 of the `ClientContext` documentation is 2.63.1, with many prior versions available, ranging down to version 2.7.1."],["`ClientContext` encapsulates client state, including the executor, credentials, and transport channel, primarily for internal use in generated code."],["The `ClientContext` class provides static methods, `create`, which allow the instantiation of the executor, credentials, and transport context from either `ClientSettings` or `StubSettings`."],["`ClientContext` offers methods such as `getBackgroundResources`, `getClock`, `getCredentials`, `getExecutor`, and `getTransportChannel` to access various components of the client's configuration."],["`ClientContext` provides methods like `getDefaultCallContext`, `getEndpoint`, `getHeaders`, `getInternalHeaders`, `getQuotaProjectId`, `getStreamWatchdog`, `getStreamWatchdogCheckInterval`, and `getTracerFactory`, to manage other various aspects of the client's environment."]]],[]]
