On that note, benchmarks against a simple ASIO http server are a must if performance is your #1 stated goal.
On that note, benchmarks against a simple ASIO http server are a must if performance is your #1 stated goal.
However performance is not the only thing oatpp has. Among with other features oatpp provides ObjectMapping layer. ObjectMapping layer enables you to do cool stuff like: - autodocument endpoints see https://medium.com/oatpp/c-oatpp-web-service-with-swagger-ui...
- easily implement custom protocols (I will write article about this later)
What I'm wondering is: Is there's a specific reason you chose to reinvent that specific wheel?
During the initial investigation boost::asio appeared to work not very good on MacOS. Problems where on the load higher than 10K concurrent connections.
There was multiple requests to compare networking performance of oatpp to ASIO lately. So I want to make full-scale testing before making statements.
Is there a way of building ASIO without Boost?