Dasynq – the event-loop library
davmac.org
Dasynq – the event-loop library
1–5 of 5 posts
Re: Dasynq – the event-loop library
#2How does it compare to others ?
Re: Dasynq – the event-loop library
#3How does it compare to others ?
Would be even more interesting if they share any production projects using it.
Re: Dasynq – the event-loop library
#4What is the advantage of this over, say, http://www.boost.org/doc/libs/1_65_1/doc/html/boost_asio.htm... ?
Networking is a main sell of boost::asio but it does general async event loops, not only for networking. And boost::asio was upgraded for C++11 years ago.
Re: Dasynq – the event-loop library
#5What is the advantage of this over, say, http://www.boost.org/doc/libs/1_65_1/doc/html/boost_asio.htm... ? Networking is a main sell of boost::asio but it does general async event loops, not only for networking. And boost::asio was upgraded for C++11 years ago.
late reply, I know - I only just saw this discussion - I didn't post this story to HN myself. However:
I recently wrote a blog post discussion why I created Dasynq, here: https://davmac.wordpress.com/2017/12/17/introducing-dasynq/
Though I don't specifically discuss boost::asio there, I believe some of the points made there apply. Also, last time I checked, boost::asio mandated linking with threads library (at least for some features) whereas Dasynq doesn't, and boost::asio didn't offer support for watching POSIX signals or child process termination (Dasynq does). Finally, the boost::asio multi-threading model is awkward, for reasons I try to explain here: https://davmac.wordpress.com/2016/06/18/boost-asio-and-resou...