You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is the inverse of #1413: an application negotiating the data channel out-of-band, but not providing an ID. This is guaranteed to not work, since one side would select an even ID and one side would select an odd ID, and they wouldn't match up. So unless I'm missing something, I think we should throw an error when this is attempted.
The text was updated successfully, but these errors were encountered:
I think we should throw an error when this is attempted.
👍 for an explicit API.
Again, I believe we should eventually unify negotiated and id unless there's a use case for having them separate (as commented here earlier). Edit (as a note to that comment): We could use a completely new field called negotiatedId and have a transitional period where current behaviour is applied in case negotiated or id is present and new behaviour in case negotiatedId is present.
This is the inverse of #1413: an application negotiating the data channel out-of-band, but not providing an ID. This is guaranteed to not work, since one side would select an even ID and one side would select an odd ID, and they wouldn't match up. So unless I'm missing something, I think we should throw an error when this is attempted.
The text was updated successfully, but these errors were encountered: