Convert PeerConnectionTracker IPC to Mojo
Reported by
vm.ar...@samsung.com,
Dec 7 2017
|
|||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: Currently PeerConnectionTracker communication happens through IPCs. What is the expected behavior? Convert PeerConnectionTracker IPC to Mojo What went wrong? Currently PeerConnectionTracker communication happens through IPCs. Did this work before? N/A Does this work in other browsers? N/A Chrome version: 62.0.3202.94 Channel: n/a OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version:
,
Dec 7 2017
,
Dec 7 2017
,
Dec 13 2017
"As the issue seems to be out of scope for triaging from TE end which is related to source code and conversion of PeerConnectionTracker IPC to Mojo, Hence adding label TE-NeedsTriageFromHYD. Thanks!"
,
Dec 13 2017
Assiging to me provisionally. Work started on http://crrev.com/c/805675
,
Dec 14 2017
guidou@, thank you.. removing 'TE-NeedsTriageFromHYD' label.
,
Feb 13 2018
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/21dda42e8b1e9040215b9e020af9b90fc655cf89 commit 21dda42e8b1e9040215b9e020af9b90fc655cf89 Author: mallikarjun82 <vm.arjun@samsung.com> Date: Tue Feb 13 17:28:24 2018 Migrate PeerConnection Tracker IPC to Mojo-part 1 This CL migrates IPC messages from renderer to browser with basic data types. This is first in upcoming CLs to migrate from IPC to Mojo. Bug: 792801 Change-Id: I79e892b4961df597c17e9ffa612be25e0d8356f9 Reviewed-on: https://chromium-review.googlesource.com/805675 Commit-Queue: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Avi Drissman <avi@chromium.org> Reviewed-by: Guido Urdaneta <guidou@chromium.org> Reviewed-by: Tom Sepez <tsepez@chromium.org> Cr-Commit-Position: refs/heads/master@{#536397} [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/browser/renderer_host/media/peer_connection_tracker_host.cc [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/browser/renderer_host/media/peer_connection_tracker_host.h [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/common/BUILD.gn [add] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/common/media/peer_connection_tracker.mojom [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/common/media/peer_connection_tracker_messages.h [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/public/app/mojo/content_browser_manifest.json [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/renderer/media/webrtc/peer_connection_tracker.cc [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/renderer/media/webrtc/peer_connection_tracker.h [modify] https://crrev.com/21dda42e8b1e9040215b9e020af9b90fc655cf89/content/renderer/media/webrtc/peer_connection_tracker_unittest.cc
,
Feb 27 2018
https://chromium-review.googlesource.com/c/chromium/src/+/930106 - Migrate PeerConnection Tracker IPC to Mojo-part 2 is under review.
,
Feb 27 2018
|
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by cm.san...@samsung.com
, Dec 7 2017Labels: -Pri-2 Pri-3