Closed tedsteen closed 11 months ago
In my opinion, I think it makes more sense to submit a PR to webrtc-rs
(to do nothing) when the credential is Unspecified
. As you've shown, it returns an error by default. Not good.
They do nothing for RTCIceCredentialType::Oauth
, I don't see why they can't the same (nothing) for Unspecified.
In my opinion, I think it makes more sense to submit a PR to
webrtc-rs
(to do nothing) when the credential isUnspecified
. As you've shown, it returns an error by default. Not good.They do nothing for
RTCIceCredentialType::Oauth
, I don't see why they can't the same (nothing) for Unspecified.
Doing nothing would also be a problem because then the password wouldn't be passed along, right?
Oh, I see now. Yeah this PR makes sense to me.
I'm still not completely sure if what webrtc-rs does is a good idea. I took the liberty of adding a commit that explains the issue and the workaround as I see it. Let me know if this matches/don't matches your understanding.
Problem: The default RTCIceCredentialType is
Unspecified
and that will eventually end up crashing when used here because the return value will be Err since thisThis PR will default to
RTCIceCredentialType::Password
. I don't know if that's what you would prefer, but it fixes my problem :)