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-04-09 UTC."],[[["The `ClientContext` class encapsulates client state, including executor, credentials, and transport channel, primarily for internal use in generated code."],["The webpage provides documentation for multiple versions of `ClientContext`, ranging from version 2.7.1 up to the latest version 2.63.1, allowing users to view documentation for specific version."],["`ClientContext` offers static methods `create` for instantiating context from `ClientSettings` or `StubSettings` and `newBuilder` for building a new context, with the first one throwing an IOException if problems occur."],["The class includes abstract methods for retrieving various configurations and resources, such as `getBackgroundResources`, `getCredentials`, `getExecutor`, and `getTransportChannel`."],["There are inherited methods from `java.lang.Object` that are available for use, along with additional static and abstract methods that make use of the various sub-components available."]]],[]]
