Ole Christian Eidheim

@SethHamilton Did you figure out your stalling issue?

Yes this is the end goal, but we have to also consider older compilers and 5-year LTS's. However, in the meanwhile, it might be that we can support `std::net` as...

You can create your own wrappers using for instance https://github.com/Naios/continuabl. I have not tried this library myself, but I found this example to be interesting: https://github.com/Naios/continuable/blob/master/examples/example-asio/example-asio.cpp. In general though, due...

Thank you, but I'm thinking that maybe in general it's a better idea to use WebSocket for this? Or is server-side-events commonly used now? It's not supported by Edge yet?...

You have Server::on_error that is called (if set) if a connection is closed prematurely.

@z0u yes, as long as you keep the `Response` object alive by copying its `shared_ptr`, the connection will remain open. The response is actually sent when the `Response` object is...

@z0u You can filter out the errors that you receive when the client closes the connection in `on_error`. But you are right, it is not strictly an error, but with...

@z0u I did a quick test, but keep in mind that I have not looked too deeply into server-sent events: ```c++ #include "server_http.hpp" using namespace std; using HttpServer = SimpleWeb::Server;...

This is also a possibility, without using threads directly: ```c++ #include "server_http.hpp" using namespace std; using HttpServer = SimpleWeb::Server; int main() { static auto io_service = make_shared(); HttpServer server; server.io_service...

I suggest that all your handlers are run using an event loop (one io_service with thread pooling set to 1 in `Server::Config`). Then you will not need to worry about...