On Mon, Jul 3, 2017 at 10:14 AM Arash Partow via Boost < boost@lists.boost.org> wrote:
Perhaps you could also add a Coverity scan to the list as well:
Yes I have seen that. The problem is that the blatantly commercial nature and build limits turns me off to it. Beast Travis scrips run every branch and pulll request through valgrind, and a separate address sanitizer and undefined behavior sanitizer. You can see it here https://travis-ci.org/vinniefalco/Beast/jobs/248185460 https://travis-ci.org/vinniefalco/Beast/jobs/248185461 Thanks -- -------------------------------------------------- On Sun, Jul 2, 2017 at 8:55 AM, Niall Douglas wrote:
..you say Beast should not provide functions to send and receive HTTP messages using Asio streams?
Absolutely correct.
Follow me on Github: https://github.com/vinniefalco