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-02 UTC."],[[["The `ClientContext` class encapsulates client state, including executor, credentials, and transport channel, primarily for internal use in generated code."],["The most recent version is 2.63.1, with many other versions available ranging from 2.62.0 to 2.7.1."],["`ClientContext` can be created using either `ClientSettings` or `StubSettings`, allowing for the instantiation of executor, credentials, and transport context."],["It provides methods to retrieve various components like background resources, clock, credentials, endpoint, executor, headers, and the transport channel."],["The class also includes methods for managing tracing and stream watchdog functionality."]]],[]]
