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"]],[["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-14 UTC."],[[["The webpage provides a list of documentation links for the `MaxPendingMessagesOption` feature across various versions of a C++ library, ranging from version 2.11.0 to the latest release candidate, 2.37.0-rc."],["`MaxPendingMessagesOption` is used to define the limit of pending messages, which are messages that have been flushed but not immediately received by the service."],["The 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."],["`MaxPendingMessagesOption` is a type alias for `std::size_t`."]]],[]]
