W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > July 2017

Re: [webrtc-pc] Deterministic behavior for transactionId validation

From: Taylor Brandstetter via GitHub <sysbot+gh@w3.org>
Date: Thu, 27 Jul 2017 14:30:17 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-318379409-1501165815-sysbot+gh@w3.org>
> Also note that the validation of parameters.encodings and any other fields should not have to rely on sender.getParameters(), as that would result in new transaction ID being generated and make the following transactionId validation behavior undefined.

Do you mean that step 7 in the `setParameters()` algorithm shouldn't actually invoke the `getParameters()` algorithm? I don't think that was ever the intention; it was just written that way for simplicity.

GitHub Notification of comment by taylor-b
Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/1488#issuecomment-318379409 using your GitHub account
Received on Thursday, 27 July 2017 14:30:26 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:21:40 UTC