Re: [boost] [beast] message bodies

Am 02.07.2017 um 20:34 schrieb Vinnie Falco via Boost:

On Sun, Jul 2, 2017 at 10:33 AM, Mike Gresens via Boost wrote:

...

As a user I'd prefer not to have string_body as a distinct type too. Same for string_view_body. Both are tightly bounded to distinct types. To be clear, Peter was asking why not `responsestd::string` which is a different but legitimate question. There are design reasons why `std::string` cannot be a choice for Body.

I'm not that sure. He gave the "dynamic_bodystd::string" example. So he wanted a body using std::string, i think.

...

So with a concept of "character sequence" we could introduce a "sequence_body" working with models like std::string, std::string_view, boost::string_ref, std::vector<char>, etc. What do you propose replacing this declaration with?

response req;

response req;" nothing to change here since using string_body = beast::http::sequence_bodystd::string; // convenience decl in beast Thanks, Mike...