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` is 2.63.1, with various prior versions available, as low as version 2.7.1."],["`ClientContext` encapsulates the client state, including the executor, credentials, and transport channel, primarily for internal use in generated code rather than by end users."],["`ClientContext` is created via the `create` static method, from either `ClientSettings` or `StubSettings`, and a builder can be used to create one with default values."],["It contains methods to access necessary properties such as `getCredentials`, `getExecutor`, `getTransportChannel`, and others, and the `getBackgroundResources` will provide the resources to close in order to clean up."],["It contains a few methods to retrieve the necessary information for the stream watchdog, and for tracing and getting headers, among other things."]]],[]]
