Closed Bug 1357689 Opened 3 years ago Closed 2 years ago

Implement nsIThreadRetargetableStreamListener in HttpChannelParent and HttpChannelParentListener

Categories

(Core :: Networking: HTTP, enhancement, P2)

enhancement

Tracking

()

RESOLVED WONTFIX

People

(Reporter: schien, Assigned: schien)

Details

(Whiteboard: [PBg-HTTP-M4][necko-triaged])

Attachments

(1 file)

To enable OMT HTTP ODA from nsHttpChannel to HttpChannelParent, both HttpChannelParent and HttpChannelParentListener need to implement nsIThreadRetargetableStreamListener.

1) For normal case, HttpChannelParentListener is able to support retargeting if all listeners on the listener chain support retargeting.

2) For channel diversion, HttpChannelParentListener need to replay ODA on main thread if retargeting is been enabled.

3) For interception, the retargeting should be disabled naturally since the intercepted channel doesn't support retargting.
Whiteboard: [necko-active][PBg-HTTP-M3] → [necko-active][PBg-HTTP-M4]
Bulk priority update: https://bugzilla.mozilla.org/show_bug.cgi?id=1399258
Priority: -- → P1
Priority: P1 → P2
Whiteboard: [necko-active][PBg-HTTP-M4] → [PBg-HTTP-M4]
No longer blocks: PBg-HTTP
Whiteboard: [PBg-HTTP-M4] → [PBg-HTTP-M4][necko-triaged]
We are moving HTTP protocol to dedicate process. After that, ODA will go from socket process to content process directly. No need to do ODA retargeting in chrome process since the IPC model is going to be changed.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.