- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Fri, 15 Jul 2022 20:41:37 +0000
- To: public-webrtc-logs@w3.org
This was added in https://github.com/w3c/webrtc-pc/pull/2033, and I think we made a mistake. As you show, it creates a race between API use and (perfect) renegotiation. No-one's implemented this, so it might be problematic to implement at this point. I propose we revert it. I think @stefhak [was right](https://github.com/w3c/webrtc-pc/issues/1940#issuecomment-406194289) that: * `direction` reflects this side's preference in offers and answers * `currentDirection` reflects the net negotiated direction E.g. it's normal for them to differ: * A `direction` of `"sendrecv"` means we have stuff to send and are open to receive * A `currentDirection` of `"sendonly"` means the other side has nothing to send at the moment In this view of them as independent attributes, updating them should be deterministic to the app. It's the nature of negotiation that changes on one side don't always produce a net result. -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2751#issuecomment-1185901962 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 15 July 2022 20:41:39 UTC