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

Overview Section #91

Jayzon opened this issue May 16, 2014 · 0 comments

Overview Section #91

Jayzon opened this issue May 16, 2014 · 0 comments


Copy link

Jayzon commented May 16, 2014

When I first read the Overview Section (currently Section 1), I felt that the paragraph below would be easier to read if a vertical list format was used.

This specification defines several objects: RTCDtlsTransport (Section 2), RTCIceTransport (Section 3), RTCIceListener (Section 4), RTCRtpSender (Section 5), RTCRtpReceiver (Section 6), RTCRtpListener (Section 7), RTCDtmfSender (Section 9), RTCDataChannel (Section 10), and RTCSctpTransport (Section 11). RTP dictionaries are described in Section 8, and the Statistics API is described in Section 12.

Also, if the Sections (above) were links to their respective Sections (Section 2, Section 3, etc.) within the specification, it may be useful.

Regarding the graphic in the Overview, I was not able to determine which side was the sender or receiver until I noticed RTPSender and RTPReceiver within the graphic.

Would it be useful to show which sides are the Sender and Receiver?

Example, we could change the top left side of the graphic from "JavaScript App" to "JavaScript App (Sender)".

Furthermore, the object names in the graphic do not contain the RTC prefix.

While the object names within the graphic are more readable to me (like it is), should there be consistency with the object names?

Example, should RtpSender be changed to RTCRtpSender etc. ?

@Jayzon Jayzon closed this as completed May 16, 2014
robin-raymond pushed a commit to robin-raymond/ortc that referenced this issue Jun 15, 2014
…cribed in Issue 57


- Added support for getRemoteCertificates(), as described in Issue 67

- Removed filterParameters and createParameters functions, as described in Issue 80

- Partially addressed capabilities issues, as described in Issue 84

Addressed WebIDL type issues described in Issue 88

- Addressed Overview section issues described in Issue 91

- Address readonly attribute issues described in Issue 92

- Added ICE restart method to address the issue described in Issue 93

- Added onerror eventhandler to sender and receiver objects as described in Issue 95
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
None yet

No branches or pull requests

1 participant