-
Notifications
You must be signed in to change notification settings - Fork 634
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add reserve() methods to dynamic buffers #1345
Comments
Are you talking about |
Yes it is http::async_read_some and I currently use boost::beast::flat_buffer. |
We have confirmed the problem you are experiencing. What you need is to call
I'll add this as a member function but it won't ship until Boost 1.70 |
Great! Thanks for a very quick response! I've tried your code and modified it to make it work. |
I've edited my response to incorporate your changes, thanks! |
fix boostorg#1345 * Add reserve() member * Add max_size() member * Revise documentation * Specify exception safety
fix boostorg#1345 * Revise documentation * Add reserve() member * Add max_size() member * Respect Allocator max_size * Specify exception safety
fix boostorg#1345 * Revise documentation * Add reserve() member * Add max_size() member * Respect Allocator max_size * Specify exception safety
fix boostorg#1345 * Revise documentation * Add reserve() member * Add max_size() member * Respect Allocator max_size * Specify exception safety
fix boostorg#1345 * Revise documentation * Add reserve() member * Add max_size() member * Respect Allocator max_size * Specify exception safety
fix boostorg#1345 * Revise documentation * Add reserve() member * Add max_size() member * Add shrink_to_fit() member * Respect Allocator max_size * Specify exception safety
fix boostorg#1345 * Revise documentation * Add reserve() member * Add max_size() member * Add shrink_to_fit() member * Respect Allocator max_size * Specify exception safety
fix boostorg#1345 * Revise documentation * Add reserve() member * Add max_size() member * Add shrink_to_fit() member * Respect Allocator max_size * Specify exception safety
It seems that async_read_some triggers the handler for every 0.5k chunk of data - is there a way to control size of it ?
The text was updated successfully, but these errors were encountered: