Hello everyone,

I have a small question regarding Boost.Asio stackless coroutines, and especially the HTTP server 4 example provided on the website (https://www.boost.org/doc/libs/1_54_0/doc/html/boost_asio/example/cpp03/http/server4/server.cpp).

I noticed that in the example, the socket_ shared pointer is being reset at every async_accept loop, basically deleting (?) the value it points to every time a new socket is accepted, since there seems to be only one shared_pointer instance, stored in a property of the server class.

How would eventual forks be able to use the newly accepted socket, if the main loop resets the pointer? Coroutine forking does not create a copy of the process like with POSIX forks (=> another shared pointer pointing to the same object); does it clone the coroutine object, along with all its properties?

 

Thanks,

Daniil Gentili