blob: 6040dc8a98c60491c170db48baad2d708d6a584e (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
|
/* This Source Code Form is subject to the terms of the Mozilla Public
* License, v. 2.0. If a copy of the MPL was not distributed with this file,
* You can obtain one at http://mozilla.org/MPL/2.0/. */
include protocol PBackground;
include protocol PContent;
include protocol PSocketProcess;
include "mozilla/layers/WebRenderMessageUtils.h";
using mozilla::wr::ByteBuffer from "mozilla/webrender/WebRenderTypes.h";
namespace mozilla {
namespace ipc {
// This is protocol is the opposite of PChildToParentStream. Please keep these
// protocols in sync.
protocol PParentToChildStream
{
manager PBackground or PContent or PSocketProcess;
child:
async Buffer(ByteBuffer aBuffer);
async Close(nsresult aRv);
parent:
// The remote stream can be used in 2 ways: it can start receiving data
// immediately after the creation of the child actor, or it can wait until
// the child stream is actually used. This second configuration is enabled by
// passing 'true' to delayedStart in AutoIPCStream CTOR.
// If we are delaying the reading, at the first use of the remote stream, we
// must activate the sending of data. This happens by calling this method.
async StartReading();
// The parent side has hit an error condition and has requested the child
// actor issue a Close() message. The close must be initiated by the child
// to avoid racing with an in-flight Buffer() message.
async RequestClose(nsresult aRv);
// Stream is always destroyed from the parent side. This occurs if the
// parent encounters an error while writing to its pipe or if the child
// signals the stream should close by SendClose().
async __delete__();
};
} // namespace ipc
} // namespace mozilla
|
