Jose wrote:
* It would be great to clarify why you based the design on a buffered stream (below are my perceived pros/cons): Pros - easy to add support for new protocols with read_until - easier header parsing Cons - increased implementation complexitiy with istreambuf - Maybe small performance penalty I'm not sure which buffered stream you're referring to here. Can you clarify?
I refer to the overall design keeping a streambuf vs a state-machine just parsing the header in one go.
I'm still not 100% sure which bit you're referring to, but if you mean the asio::streambuf usage in http_read_stream, that's just to keep the implementation simple. Any overhead there only applies to receiving the headers, and isn't incurred once you start downloading the content. Cheers, Chris