After a publisher flushes a batch of messages the batch is (obviously) not received immediately by the service. While the batch remains pending it potentially consumes memory resources in the client (and/or the service).
Some applications may have constraints on the number of bytes and/or messages they can tolerate in this pending state, and may prefer to block or reject messages.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-08-14 UTC."],[[["\u003cp\u003eThe webpage provides a list of documentation links for the \u003ccode\u003eMaxPendingMessagesOption\u003c/code\u003e feature across various versions of a C++ library, ranging from version 2.11.0 to the latest release candidate, 2.37.0-rc.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingMessagesOption\u003c/code\u003e is used to define the limit of pending messages, which are messages that have been flushed but not immediately received by the service.\u003c/p\u003e\n"],["\u003cp\u003eThe feature relates to managing client-side memory usage and message flow control by allowing applications to set constraints on the number of pending messages, potentially blocking or rejecting new messages if limits are reached.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eMaxPendingMessagesOption\u003c/code\u003e is a type alias for \u003ccode\u003estd::size_t\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
