Darren Cook's review

[vinipsmaker]

• Better documentation, better marketed and much more examples.

• High-level API.

• Header-only

• A built-in router.

• Benchmarks.

  I would like to see CPU and memory usage benchmarks; ideally on reference hardware such as an Amazon EC2 instance. Realistic examples such as: a simple file server, a file-server that is doing substitution/modification of the files being read, and a chat server. This is because artificial benchmarks often encourage making the design harder to use for the sake of a few microseconds. I'd rather have a server, doing real work, that can support 499 clients/second than one that can support 500 clients/second but requires me to write twice as much code.

About HttpClient

Good inspirations:

• cURL.
• PHP's file_get_contents.

WON'T FIX

• It should be called Boost.HttpServer; and then there should be another library called Boost.HttpClient.