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."],["`ClientContext` offers static methods, `create` and `newBuilder`, to instantiate or construct new instances based on `ClientSettings` or `StubSettings`."],["The `ClientContext` class has methods to retrieve various properties, including the background resources, clock, credentials, default call context, endpoint, executor, and more."],["The `ClientContext` also provides methods for getting details related to tracing and stream watchdog functionality, with `getTracerFactory` and `getStreamWatchdog` respectively."],["This page provides documentation for the `ClientContext` class and a list of available versions, ranging from the latest `2.63.1` down to `2.7.1`."]]],[]]
