![]() Most status alerts should have priorities above normal level. Good reason for this is resume data verification case. For a large torrent(having lots of pieces) whole alert queue will be overflowed with a `piece_finished_alert` right after resume data has been verified. Thus alerts like `torrent_checked_alert`, `torrent_finished`, `state_changed_alert` will not go the alerts queue. * Introduce alert_priority enumeration * Bump state_changed_alert's priority * Set dht_direct_response_alert priority to `critical` |
||
---|---|---|
.. | ||
libtorrent |