| ChannelEventQueue.cpp |
|
6287 |
- |
| ChannelEventQueue.h |
|
13174 |
96 % |
| DocumentChannel.cpp |
|
15924 |
- |
| DocumentChannel.h |
DocumentChannel is a protocol agnostic placeholder nsIChannel implementation
that we use so that nsDocShell knows about a connecting load. It transfers
all data into a DocumentLoadListener (running in the parent process), which
will create the real channel for the connection, and decide which process to
load the resulting document in. If the document is to be loaded in the
current process, then we'll synthesize a redirect replacing this placeholder
channel with the real one, otherwise the originating docshell will be removed
during the process switch.
|
4039 |
88 % |
| DocumentChannelChild.cpp |
|
16875 |
- |
| DocumentChannelChild.h |
DocumentChannelChild is an implementation of DocumentChannel for nsDocShells
in the content process, that uses PDocumentChannel to serialize everything
across IPDL to the parent process.
|
2489 |
100 % |
| DocumentChannelParent.cpp |
ObjectUpgradeHandler |
6105 |
- |
| DocumentChannelParent.h |
An actor that forwards all changes across to DocumentChannelChild, the
nsIChannel implementation owned by a content process docshell.
|
2000 |
100 % |
| DocumentLoadListener.cpp |
ANDROID |
133292 |
- |
| DocumentLoadListener.h |
DocumentLoadListener represents a connecting document load for a
CanonicalBrowsingContext (in the parent process).
It creates a network channel for the document load and then waits for it to
receive a response (after all redirects are resolved). It then decides where
to handle that load (could be in a different process from the initiator),
and then sets up a real network nsIChannel to deliver the data to the final
destination docshell, maybe through an nsIParentChannel/nsIChildChannel IPDL
layer.
In the case where this was initiated from an nsDocShell, we also create an
nsIChannel to act as a placeholder within the docshell while this process
completes, and then notify the docshell of a 'redirect' when we replace this
channel with the real one.
|
26710 |
84 % |
| InputChannelThrottleQueueChild.cpp |
|
859 |
- |
| InputChannelThrottleQueueChild.h |
|
930 |
- |
| InputChannelThrottleQueueParent.cpp |
stabilize |
3684 |
- |
| InputChannelThrottleQueueParent.h |
|
1357 |
0 % |
| moz.build |
|
3170 |
- |
| NeckoChannelParams.ipdlh |
|
24183 |
- |
| NeckoChild.cpp |
|
6380 |
- |
| NeckoChild.h |
Reference to the PNecko Child protocol.
Null if this is not a content process.
|
2447 |
100 % |
| NeckoCommon.cpp |
|
2171 |
- |
| NeckoCommon.h |
|
5563 |
100 % |
| NeckoMessageUtils.h |
|
6421 |
81 % |
| NeckoParent.cpp |
|
35574 |
- |
| NeckoParent.h |
Creates LoadContext for parent-side of an e10s channel.
PContentParent corresponds to the process that is requesting the load.
|
8970 |
100 % |
| NeckoTargetHolder.cpp |
|
1017 |
- |
| NeckoTargetHolder.h |
|
1273 |
100 % |
| ParentChannelWrapper.cpp |
|
3347 |
- |
| ParentChannelWrapper.h |
|
1234 |
40 % |
| ParentProcessDocumentChannel.cpp |
|
11628 |
- |
| ParentProcessDocumentChannel.h |
|
2167 |
100 % |
| PDocumentChannel.ipdl |
|
2117 |
- |
| PInputChannelThrottleQueue.ipdl |
|
467 |
- |
| PNecko.ipdl |
Establish a connection between generic redirect channels which do not need
specialized nsIParentChannel handling.
|
6406 |
- |
| PProxyAutoConfig.ipdl |
|
595 |
- |
| PProxyConfigLookup.ipdl |
|
493 |
- |
| ProxyAutoConfigChild.cpp |
|
6537 |
0 % |
| ProxyAutoConfigChild.h |
|
2592 |
0 % |
| ProxyAutoConfigParent.cpp |
|
598 |
0 % |
| ProxyAutoConfigParent.h |
|
725 |
0 % |
| ProxyConfigLookup.cpp |
|
3292 |
- |
| ProxyConfigLookup.h |
|
1203 |
- |
| ProxyConfigLookupChild.cpp |
|
1350 |
- |
| ProxyConfigLookupChild.h |
|
1147 |
- |
| ProxyConfigLookupParent.cpp |
|
1364 |
- |
| ProxyConfigLookupParent.h |
|
856 |
0 % |
| PSocketProcess.ipdl |
tabId is only required for web-proxy support, which isn't always needed |
9216 |
- |
| PSocketProcessBackground.ipdl |
PSocketProcessBackground is the top level IPC protocol between
a background task queue in the socket process and the parent process.
We use this to create several IPC protocols between the socket process
and the parent process.
|
1770 |
- |
| PSocketProcessBridge.ipdl |
PSocketProcessBridge is the IPC protocol between the main thread in
the content process and the main thread in the socket process.
We use this to create PBackgroundDataBridge and PMediaTransport protocols
between content process and socket process.
Once created, PSocketProcessBridgeChild is the actor that lives in
content process and PSocketProcessBridgeParent lives in
socket process.
|
1410 |
- |
| SocketProcessBackgroundChild.cpp |
|
3436 |
- |
| SocketProcessBackgroundChild.h |
|
1504 |
- |
| SocketProcessBackgroundParent.cpp |
|
6562 |
- |
| SocketProcessBackgroundParent.h |
|
1970 |
- |
| SocketProcessBridgeChild.cpp |
|
6305 |
- |
| SocketProcessBridgeChild.h |
|
1722 |
- |
| SocketProcessBridgeParent.cpp |
|
3276 |
- |
| SocketProcessBridgeParent.h |
|
1412 |
- |
| SocketProcessChild.cpp |
static |
28207 |
- |
| SocketProcessChild.h |
|
7727 |
100 % |
| SocketProcessHost.cpp |
remoteType |
8746 |
- |
| SocketProcessHost.h |
|
4715 |
70 % |
| SocketProcessImpl.cpp |
|
1954 |
- |
| SocketProcessImpl.h |
|
980 |
100 % |
| SocketProcessLogging.h |
|
616 |
- |
| SocketProcessParent.cpp |
static |
13349 |
- |
| SocketProcessParent.h |
|
4629 |
100 % |