diff options
| author | imcheng@chromium.org <imcheng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-07 11:26:28 +0000 |
|---|---|---|
| committer | imcheng@chromium.org <imcheng@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2014-03-07 11:26:28 +0000 |
| commit | f44823ce60dc63a2835765f584ba76a484c89839 (patch) | |
| tree | 21bac700b6fae02fcdc93955606396755bc46295 /crypto/capi_util.h | |
| parent | 1e68ed1cfcb9eba851d46c54a5b79da8186a89e9 (diff) | |
| download | chromium_src-f44823ce60dc63a2835765f584ba76a484c89839.zip chromium_src-f44823ce60dc63a2835765f584ba76a484c89839.tar.gz chromium_src-f44823ce60dc63a2835765f584ba76a484c89839.tar.bz2 | |
Cast: IPC from browser to renderer to send packet events from transport to cast library.
- Added a new IPC message: CastMsg_RawEvents
- Transmit cast logging settings to transport on browser side by adding a new field in CastTransportConfig.
- Install a LoggingImpl on transport side
-- If raw event logging is enabled, install a SimpleEventSubscriber to capture packet events.
-- If raw event logging is enabled, a RepeatingTimer will be started to call the subscriber to collect packet events and send back to cast library via the IPC.
NOTE: Currently, no actual packet events are logged on the transport. That will be in the next CL. There are two ways to do this:
- Pass LoggingImpl to sub components on the transport (paced_sender, rtp_packetizer, etc.)
- Pass a callback that will be propagated down and invoked at the right place.
BUG=343992
Review URL: https://codereview.chromium.org/178073004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@255579 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'crypto/capi_util.h')
0 files changed, 0 insertions, 0 deletions