Closed Bug 1138326 Opened 10 years ago Closed 9 years ago

[RTSP] Move RTSP logic to child process

Categories

(Firefox OS Graveyard :: RTSP, defect)

x86_64
Gonk (Firefox OS)
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: jhao, Assigned: jhao)

References

Details

This is to avoid bugs crashing the parent process, causing the device to reboot.
As you can see in this diagram, RtspControllerParent, RtspController, RTSPSource, RtspConnectionHandler are in parent process. What isn't shown in this diagram is that RtspConnectionHandler sends request by ARTSPConnection and receive RTP packets by ARTPConnection. If we want to move all the RTSP related code to child process, including ARTPConnection and ARTSPConnection. We'll have to use TCP Socket in child process. However, the patch in bug 950660 is not ready yet. An idea is to move just the RtspControllerParent, RtspController, RTSPSource, and RtspConnectionHandler to child process, since they contain the most of the logic, and leave ARTPConnection and ARTSPConnection in the parent process. Then, we wouldn't need the patch in bug 950660. The drawback of the idea is that we have to design a new IPC interface. Also, by the time bug 950660 is resolved, we may have to change the structure all over again.
Depends on: 950660
(In reply to Jonathan Hao [:jhao] from comment #1) > As you can see in this diagram, RtspControllerParent, RtspController, > RTSPSource, RtspConnectionHandler are in parent process. Jonathan, you forgot to attach the link of diagram.
(In reply to Ethan Tseng [:ethan] from comment #2) > Jonathan, you forgot to attach the link of diagram. Oops! Here it is https://wiki.mozilla.org/File:Close_RtspMediaResource.jpg
Bug 950660 (Support TCP nr_socket in content process) was resolved fixed, which means we are able to use TCP socket in child process now. Perhaps it is worth to proceed this refactoring bug.
Closing this bug since no one works on RTSP anymore.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.