Create IPC between ContentProcess and SocketProcess

RESOLVED FIXED

Status

()

enhancement
P1
normal
RESOLVED FIXED
7 months ago
5 months ago

People

(Reporter: kershaw, Assigned: kershaw)

Tracking

(Blocks 1 bug)

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [necko-triaged])

Attachments

(1 attachment)

(Assignee)

Description

7 months ago
As per bug 1484743 comment #0, we might nned to deliver data directlyt from socket process to content process.

The goal of this bug is to create a bridge between content process and socket process.
(Assignee)

Updated

7 months ago
Assignee: nobody → kershaw
Priority: -- → P2
Whiteboard: [necko-triaged]
(Assignee)

Updated

7 months ago
Blocks: socket-proc
(Assignee)

Updated

7 months ago
Summary: Create IPC between HttpChannelChild and SocketProcess → Create IPC between ContentProcess and SocketProcess
(Assignee)

Comment 1

7 months ago
1. Introduce an empty top level IPC protocol PSocketProcessBridge
2. PSocketProcessBridgeParent lives in content process and PSocketProcessBridgeChild lives in socket process.
3. NeckoParent will try to create the bridge when |RecvPHttpChannelConstructor| is called.
Kershaw, does this patch blocks any immediate work?  I want to prioritize the review, it's not a small patch.  Thanks.
Flags: needinfo?(kershaw)
(Assignee)

Comment 3

7 months ago
(In reply to Honza Bambas (:mayhemer) from comment #2)
> Kershaw, does this patch blocks any immediate work?  I want to prioritize
> the review, it's not a small patch.  Thanks.

There is no need to review this for now.
This patch does't block any work.
Flags: needinfo?(kershaw)
(Assignee)

Updated

7 months ago
Priority: P2 → P3
Blocks: 1503834
Priority: P3 → P2
Blocks: socket-proc-webrtc
No longer blocks: socket-proc
Kershaw, can you please update the patch here according https://phabricator.services.mozilla.com/D7165#282051 (nothing major, I believe) and when the added assertions pass, land on larch?  You may want to ping :bwc before landing, to sync with his local work based on larch first, though.

Thanks.
Flags: needinfo?(kershaw)
Priority: P2 → P1
No longer blocks: socket-proc-webrtc
(Assignee)

Comment 5

5 months ago
(In reply to Honza Bambas (:mayhemer) from comment #4)
> Kershaw, can you please update the patch here according
> https://phabricator.services.mozilla.com/D7165#282051 (nothing major, I
> believe) and when the added assertions pass, land on larch?  You may want to
> ping :bwc before landing, to sync with his local work based on larch first,
> though.
> 
> Thanks.

Patch updated.
Flags: needinfo?(kershaw)
(Assignee)

Comment 6

5 months ago
https://hg.mozilla.org/projects/larch/rev/9670668f3972d6e149322f3d14a3d91be4591c71
Status: NEW → RESOLVED
Last Resolved: 5 months ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.