On 10/02/2017 12:06 AM, Vinnie Falco wrote:
> However, I came up with a very simple technique to make this work with
> Beast by writing just a tiny bit of extra code. The solution is to
> implement a stream wrapper which meets the requirements of
> SyncReadStream[1] and/or AsyncReadStream[2] and forwards the calls to
> read to the "next layer" object, which will be the actual socket or
> ssl::stream.
Sounds like a good solution.
