Connections need to perform background work on behalf of the application. Normally they just create a background thread and a CompletionQueue for this work, but the application may need more fine-grained control of their threads.
In this case the application can provide its own BackgroundThreadsFactory and it assumes responsibility for creating one or more threads blocked on its CompletionQueue::Run().
[[["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-05 UTC."],[[["The latest version available is 2.37.0-rc, with numerous prior versions listed for reference, including 2.36.0 down to 2.10.1."],["Applications can use `BackgroundThreadsFactory` to gain more control over their threads that perform background work, rather than using default background thread creation and `CompletionQueue`."],["If the application provides its own `BackgroundThreadsFactory`, it needs to create at least one thread that is blocked on its `CompletionQueue::Run()`."],["`GrpcBackgroundThreadPoolSizeOption`, `GrpcCompletionQueueOption`, and `GrpcBackgroundThreadsFactoryOption` are mutually exclusive, with `GrpcBackgroundThreadsFactoryOption` being ignored when `GrpcCompletionQueueOption` is configured."],["The documented `BackgroundThreadsFactory` type is an alias of `BackgroundThreadsFactory`."]]],[]]
