multi_buffer implementation change (API Change):

fix #440

WARNING

multi_buffer constructor now takes a maximum size instead of the
"allocation size". This is a breaking change. The allocation size
feature is removed. To update calling code, remove the allocation
size parameter from call sites.

* multi_buffer now uses a geometric growth algorithm for better performance.
This commit is contained in:
Vinnie Falco committed 2017-06-08 19:36:51 -07:00
1 parent dd7f5c03f8
commit 58c2739115
9 files changed
+235 -270

No files matched your search

+1 -1
View File
@@ -40,7 +40,7 @@ public:
"0123456789abcdef" "0123456789abcdef" "0123456789abcdef" "0123456789abcdef"
"0123456789abcdef" "0123456789abcdef" "0123456789abcdef" "0123456789abcdef"
"0123456789abcdef" "0123456789abcdef" "0123456789abcdef" "0123456789abcdef";
multi_buffer b(512);
multi_buffer b;
ostream(b) << s;
BEAST_EXPECT(boost::lexical_cast<std::string>(
buffers(b.data())) == s);