Niall Douglas's review

[vinipsmaker]

• [ ] C++98 support.
• [ ] Macros for C++11 (e.g. optionally expose std::error_code).
• [x] Remove CMake.
• [x] Header-only.
• [ ] Regularly input fuzz tested. american fuzzy lop or LLVM libfuzzer at least weekly on a CI.
• [ ] queue_socket isn't standard and causes confusion. It deserves more attention in documentation (...a page just documenting composed operations...).
• [ ] queue_socket should be provided (I don't think queue sockets should be a concept, I think they need to be the core of your library's user facing API....).

• [ ] You've not convinced me why I should use your library and not write some ad hoc code which would be "good enough".

  You've not convinced me why I should use your library and not an alternative, including one written in Python or PHP.

  At the front of your docs, you need to have me convinced by the end of page 2 that there is no better library than yours, including on other languages. Evidence such as an excellent literature review covering alternatives and benchmarks between your code and alternatives are steps in the right direction.

• [ ] What alternatives may be better suited for the user examining Http for suitability and why? i.e. make your documentation useful to people with a problem to solve, not just a howto manual.
• [ ] Benchmarks, especially latency ones which are important for many uses of HTTP are missing. I'd particularly like to know confidence intervals on the statistical distribution so I know worst case outcomes.
• [ ] Tutorials that incrementally show how to build a full application ("Personally speaking, I'd like if in your tutorial you took ten self-contained steps in building a simple HTTP fileserver, each with a finished working program at the end of each section. Like the ASIO tutorial does. In particular, I'd like to see layers which add on etags and other of the fancy facilities in stages.").
• [ ] HTTP/2.0.
• [ ] CI testing with valgrind
• [ ] thread sanitiser
• [ ] coveralls.io coverage testing
• [ ] Documentation improvement on the design ideas (The pipeline has the following requests... is missing and pipelining causes too much confusion still).
• [x] Avoid nesting too many [section] blocks.
• [ ] easy API like the above for Python's urllib3 (example from Niall show HTTP client code).

  Hints

• See http://www.python-requests.org/en/latest/api/ for HTTP client
• Ideas to write examples and to benchmark
  • Implementing an ICAP filter for Squid. See http://wiki.squid-cache.org/Features/ICAP. Let's say it prepends to the <title> tag content something funny.
  • Bjorn has probably also mentioned this, but the world's simplest WebDAV server (https://en.wikipedia.org/wiki/WebDAV) serving a single read-only file called HelloWorld.txt would be great. Being able to mount your HTTP library as a Windows or Linux drive is simply cool.

    WON'T FIX

• Boost-less version of Boost.Http.
• Explain why Boost.Http uses Asio.

[vinipsmaker]

Avoid nesting too many [section] blocks.

Done, but boostbook still generates verbose TOC that I'd like to avoid.

[vinipsmaker]

Avoid nesting too many [section] blocks.

I've just converted documentation from Boost's QuickBook to asciidoc: https://github.com/BoostGSoC14/boost.http/commit/c535bf73cab03b60b285df7e7bff62c49be99744

I shouldn't have troubles with QuickBook anymore.