Ole Christian Eidheim

Last time I studied this I came to the conclusion that calling [ssl::stream::shutdown](http://www.boost.org/doc/libs/1_66_0/doc/html/boost_asio/reference/ssl__stream/shutdown.html) was not needed. Though I might be wrong! By the way, [ssl::stream](http://www.boost.org/doc/libs/1_66_0/doc/html/boost_asio/reference/ssl__stream.html) does not have a `close`-member...

Although, thank you for bringing this up. I'll add a couple of labels to this issue.

I did a quick implementation here: ```c++ #include "server_http.hpp" using HttpServer = SimpleWeb::Server; int main() { HttpServer server; server.config.port = 8080; std::thread server_thread([&server] { server.start(); }); { // Wait till...

@jschrotter you are right. This is hopefully a better solution: ```c++ #include "server_http.hpp" using HttpServer = SimpleWeb::Server; int main() { HttpServer server; server.config.port = 8080; server.io_service = std::make_shared(); std::thread server_thread([&server]...

It's a good idea, and I have thought about it, but the main issue is added complexity. Also, last time I had a look at the HTTP2 standard, the documentation...

@Type1J Thank you for the information, I'll have to look into this during the summer.

Brilliant! Would you mind creating a pull request so that you get credited for this:)?

I think these changes should work without creating a buffer for each send operation, although c++14 is required here: ```diff diff --git a/http_examples.cpp b/http_examples.cpp index 3e16a9c..39ad46c 100644 --- a/http_examples.cpp +++...

In general, it is best to use an event loop (one server thread) so that all the handlers that you define always will be run sequentially. But this does not...

~~Here is an another attempt, where the number of buffers created equals the maximum number of threads the handlers are run in:~~  edit: removed flawed diff