Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

setParameters: Do argument checks in sync section and specify parellel steps #1560

Merged
merged 4 commits into from
Sep 28, 2017

Conversation

adam-be
Copy link
Member

@adam-be adam-be commented Aug 24, 2017

First stab, do not merge yet. We need to figure out what goes into the parallel steps.

fix #1520


Preview | Diff

@adam-be adam-be changed the title setParameters: Do argument checks in sync section setParameters: Do argument checks in sync section and specify parellel steps Sep 12, 2017
Copy link
Contributor

@taylor-b taylor-b left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just some minor comments.

<tr>
<td><dfn><code>hardware-encoder-error</code></dfn></td>
<td>The hardware encoder resources required for the requested
operation are not available.</td>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"... or the hardware encoder doesn't support the provided set of parameters"? Those could feasibly be two separate errors.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Raised a separate issue for this question #1602

webrtc.html Outdated
<li>Resolve <var>p</var> with <code>undefined</code>.</li>
<li>Let <var>p</var> be a new promise.</li>
<li>In parallel, configure the media stack to use
<var>parameters</var> to transmit <var>sender</var>.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: It's not sender that's being transmitted, it's sender's track.

webrtc.html Outdated
created <code><a>RTCError</a></code> whose
<code>errorDetail</code> set to
"hardware-encoder-error".</li>
</ol>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we need a catchall "OperationError" if something non-hardware-related failed in the async steps?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let's add that. Hopefully it wouldn't be used much if we have a rather complete list of specific errors.

webrtc.html Outdated
<li>If an error occurred due to hardware resources not
being available, reject <var>p</var> with a newly
created <code><a>RTCError</a></code> whose
<code>errorDetail</code> set to
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"is set to"

@adam-be
Copy link
Member Author

adam-be commented Sep 15, 2017

Thanks for reviewing @taylor-b. New (and rebased) iteration coming up.

@stefhak stefhak merged commit 35a3a09 into master Sep 28, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

setParameters does input validation in parallel, and doesn't actually apply parameters?
4 participants