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 latest version available is 2.63.1, and the content lists versions down to 2.7.1, offering a range of historical versions for `ClientContext`."],["`ClientContext` encapsulates client state, including executor, credentials, and transport channel, for internal use in generated code, and most users won't directly interact with it."],["`ClientContext` offers static methods to create instances from `ClientSettings` or `StubSettings`, along with a `newBuilder()` method to create a new `ClientContext.Builder` instance."],["The class provides abstract methods to retrieve components like background resources, clock, credentials, call context, endpoint, executor, headers, tracer factory, and the transport channel."],["`ClientContext` has methods for managing resources and operations, like `getBackgroundResources()` for clean-up and `getStreamWatchdog()` for stream health checks, alongside several other similar management methods."]]],[]]
