Re: [boost] [beast] A Networking-TS version of Boost.Asio and Boost.Beast is here!

Subject: Re: [boost] [beast] A Networking-TS version of Boost.Asio and Boost.Beast is here!
From: Vinnie Falco (vinnie.falco_at_[hidden])
Date: 2017-10-04 13:39:44

On Tue, Oct 3, 2017 at 2:23 PM, paul <pfultz2_at_[hidden]> wrote:
> How do the Buffer concepts change to depend on networking? The way the buffers
> are defined now, there is no dependency on Boost.Asio.

Are you suggesting that the Net-TS buffer concepts do not depend on
Boost.Asio? That's not entirely correct.

Net-TS buffer sequence iterator value types must be convertible to
`std::experimental::net::const_buffer` or
`std::experimental::net::mutable_buffer`. In the Net-TS compatible
version of Asio these types are  `boost::asio::const_buffer` and
`boost::asio::mutable_buffer`.

There is simply no way to avoid the dependency on these concrete types
in Asio. In my other post I am proposing a library Boost.Buffers to
work around this problem, so that people (like me) can write libraries
which use only Asio buffer concepts, without a dependency on all of
Asio (and everything that Asio depends on, recursively).

Thanks