mirror of https://github.com/sipwise/sems.git
If the owner of the `RegThread` (`RegistrationAgentFactory`) was asked to be destructed, make the destroy process of the reg thread more ordered as well. That makes the thread to stop as soon as the app factory begins its own destruction. This will help to avoid a possible way to end up with a stale (or invalid) DI factory ptr. E.g.: `RegThread` keeps on running, while all the plugins are being torn down by that time already. In this case the `RegThread` can simply call `getFactory4Di()` or `di_f->getInstance()` way after the registrar_client is already partially destroyed. Change-Id: I10e38174d3856e19f2696f8d874ea166e0a035a8mr26.2
parent
e9995a63f9
commit
a654c9c01d
Loading…
Reference in new issue