From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2019-12-05 13:39:28
Folks, we are way overthinking the behavior of resize() over
capacity(). It throws for a very simple reason. The most obvious and
common optimization for highly concurrent network programs is simply
to avoid the global allocator. And the obvious and common mitigation
for resource exhaustion attacks is to limit the amount of data that an
I/O handler is allowed to process.
Using a fixed string as a temporary buffer for an algorithm satisfies
both of these goals, and it does so without the caller having to write
a bunch of code to check sizes in advance.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk