tree e91885881f1db3535378a7e82323792407609b14
parent 5ae4b692fcee7d27c1e1a5a7c6efbd375a76dacc
author Ed Tanous <edtanous@google.com> 1638559493 -0800
committer Ed Tanous <ed@tanous.net> 1639599618 +0000

Make timer system use boost

The original crow timeout system had a timer queue setup for handling
many thousands of connections at a time efficiently.  The most common
use cases for the bmc involve a handful of connections, so this code
doesn't help us much.

These days, boost asio also implements a very similar timer queue
https://www.boost.org/doc/libs/1_72_0/boost/asio/detail/timer_queue.hpp
internally, so the only thing we're loosing here is the "fuzzy"
coalescing of timeout actions, for which it's tough to say if anyone
will even notice.

This commit implements a timer system that's self contained within each
connection, using steady_timer.  This is much more "normal" and how most
of the beast examples implement timers.

Tested:
Minimal touch testing to ensure that things work, but more testing is
required, probably using sloworis to ensure that our timeouts are no
longer issues.

Signed-off-by: Ed Tanous <edtanous@google.com>
Change-Id: I19156411ce46adff6c88ad97ee8f6af8c858fe3c