New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 591867 link

Starred by 1 user
Status: Duplicate
Merged: issue 569259
Owner:
█ x...@chromium.org
Last visit > 30 days ago
Closed: Mar 2016
Cc:
m...@chromium.org
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Feature



Sign in to add a comment

Clean up cast IPC messages

Project Member Reported by x...@chromium.org, Mar 4 2016 
Currently all RTCP packets are built and parsed in the browser process.
All info to build the RTCP packet and the messages after parsing need to 
be sent over IPC.
The building and parsing RTCP packets can be moved to the render, and only packets are sent over IPC. A bunch of IPC messages can be removed.

Comment 1 by x...@chromium.org, Mar 5 2016

Mergedinto: 569259
Status: Duplicate (was: Started)
For now we will only move the receiver RTCP session to the render. As on the sender side, the sender RTCP report needs the RTP sender's packet count and octet count which are unknown in the render. The cast feedback is also needed to decide which packets to be resent. So decided to still keep the sender RTCP session in the browser process. Merged into  issue 569259 .
►

Sign in to add a comment