BuffersGenerator A [*BuffersGenerator] provides a generalized interface for generating serialized data for sequential processing. The generator will be asked to produce buffers. The consuming code will signal how much of the data has been consumed, and repeatedly query for buffers until no more data is available, or the generator indicates an error condition. In this way, serializers can be adapted as [*BuffersGenerator], for example [link beast.ref.boost__beast__http__message_generator `http::message_generator`] which provides a type-erased interface for a variety of concrete http message types. Overloads of [link beast.ref.boost__beast__write `write`] and [link beast.ref.boost__beast__async_write `async_write`] operations are provided as free functions. These operations will consume the output of a [*BuffersGenerator] and process the data by writing them to a __SyncWriteStream__ or __AsyncWriteStream__ respectively. Associated Types * [link beast.ref.boost__beast__is_buffers_generator `is_buffers_generator`]\n* __ConstBufferSequence__ Requirements In this table: * `G` denotes a type meeting the requirements of [*BuffersGenerator].\n* `g` denotes a value of type `G`.\n* `c` denotes a possibly-const value of type `G`.\n* `n` is a value of type `std::size_t`.\n* `ec` is a value of type [link beast.ref.boost__beast__error_code `error_code&`]. Valid expressions Expression Type Semantics, Pre/Post-conditions `G::const_buffers_type` A type which meets the requirements of __ConstBufferSequence__. This is the type of buffer returned by `g.prepare(ec)`. `c.is_done()` `bool` Called to ask the generator for its completion status.\n\nA generator has completed when no new buffer will be produced and previously produced buffers have been fully consumed.\n\n[*Note:] The result of invoking `prepare` on `g` once it has completed is unspecified. `g.prepare(ec)` Called to ask the generator to produce buffers containing data for processing.\n\nThe returned value is the __ConstBufferSequence__ representing unconsumed data.\n\nThe function will ensure that `ec.failed()` is `false` if there was no error or set to the appropriate error code if there was one.\n\nIf no unconsumed data is available, this operation shall make progress to eventually reach completion.\n\nThe result of invoking `prepare` after completion or encountered error(s) is defined by the generator implementation. It can not be assumed to be meaningful or safe to do so, in general.\n\nThe capacity of the buffer returned is defined by the generator implementation.\n\n[*Note:] Any buffers obtained by previous calls to `prepare` are invalidated. `g.consume(n)` This function is called to signal that the consumer (caller) of the generator has processed part of the data returned by the previous call to `prepare`.\n\nThe value of `n` indicates how much of the data processed (in bytes).\n\nWhen `n` exceeds the number of bytes returned from the last call to `prepare`, `consume` shall behave as if `n` was equal to that number.\n\nRemaining unconsumed data will be returned from subsequent calls to `prepare`.\n\n[*Note:] Any buffers obtained by previous calls to `prepare` are invalidated. `is_buffers_generator<G>` `std::bool_constant` An alias for `std::true_type` for `G`, otherwise an alias for `std::false_type`. Exemplar ``` ``` Models * [link beast.ref.boost__beast__http__message_generator `http::message_generator`] Algorithms * [link beast.ref.boost__beast__async_write `async_write`]\n* [link beast.ref.boost__beast__write `write`]