sdp-anatomy | Source code for webrtcHacks ' Anatomy of a SDP | Video Utils library
kandi X-RAY | sdp-anatomy Summary
kandi X-RAY | sdp-anatomy Summary
Source code for webrtcHacks' Anatomy of a SDP
Support
Quality
Security
License
Reuse
Top functions reviewed by kandi - BETA
- generate the display data
sdp-anatomy Key Features
sdp-anatomy Examples and Code Snippets
Community Discussions
Trending Discussions on sdp-anatomy
QUESTION
I am trying to build a chat app between two browsers without a signal server with WebRTC. The manual offer-answer process is most difficult part of the task.
It occurred to me that most SDP data generated by new RTCPeerConnection().createOffer()
as in RTCSessionDescription.sdp
is redundant.
Reference: https://webrtchacks.com/sdp-anatomy/
I tested, the o=
line can be striped like o=- 1 2 IN IP4 127.0.0.1
and it works totally fine, the a=candidate:
line contains FOUNDATION identifier and priority are completely useless, supposedly there's only one candidate in my case.
My question is, for the simple (and insecure) chat app between two browsers without ICE, can we strip down a=ice-pwd:
line and a=fingerprint:
line? The rest of SDP looks identical and can be just hard-coded into both peers.
ANSWER
Answered 2021-Jan-28 at 18:47That question came up on WebRTCHacks before: https://webrtchacks.com/the-minimum-viable-sdp/ There haven't been that many changes since 2015 so it should still apply.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install sdp-anatomy
Support
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page