When peer cert fingerprint does not match the one provided in SDP we will move to the failed state and stop the PeerConnection process for now.
The question is if we should stick to the permanent restart strategy in a GenServer as it makes Supervisor always restart our GenServer, even when exited with :normal, :shutdown or {:shutdown, term} reasons.
For now, I left this to be configured by a user using Supervisor.child_spec.
When peer cert fingerprint does not match the one provided in SDP we will move to the failed state and stop the PeerConnection process for now.
The question is if we should stick to the
permanent
restart strategy in a GenServer as it makes Supervisor always restart our GenServer, even when exited with:normal
,:shutdown
or{:shutdown, term}
reasons.For now, I left this to be configured by a user using
Supervisor.child_spec
.