On Fri, Aug 14, 2015 at 1:49 AM, Lee Clagett
On Thu, Aug 13, 2015 at 11:16 PM, VinÃcius dos Santos Oliveira < vini.ipsmaker@gmail.com> wrote:
2015-08-13 22:19 GMT-03:00 Lee Clagett
: Fair enough. I didn't document this behaviour. I'll gather all these points after the review period to implement these improvements.
About the embedded device situation, it'll be improved when I expose the parser options, then you'll be able to set max headers size, max header name size, mas header value size and so on. With all upper limits figured out, you can provide a single chunk of memory for all data.
But what if an implementation wanted to discard some fields to really keep the memory low? I think that was the point of the OP. I think this is difficult to achieve with a notifying parser. It might be overkill for Boost.Http, people under this durress can seek out existing Http parsers.
*without a notfying parser